SYS_GUID and UUID

Generates and returns a new globally unique identifier (GUID) each time it is called.

Syntax

SYS_GUID()
UUID()

Return Type

SYS_GUID: BINARY(16)

UUID: VARCHAR(36)

Remarks

  • Returns a v4 UUID

  • The value returned will be globally unique

  • A new value will be produced for each row processed

  • A new value will be produced for each occurrence of the function in the query syntax

  • UUID works exactly like SYS_GUID except for the return type

  • SYG_GUID/UUID cannot be used as a default column value for a sharded table

  • SYS_GUID/UUID cannot be used in a computed column expression in a table definition

Note

Use INT or BIGINT fields for joining tables if performance is the most important consideration. Joining on BINARY(16) columns works, but is noticeably slower. Rather than UUID or SYS_GUID, use AUTO_INCREMENT, or implement application code to provide integer key values on which to join tables, for the best performance.

Examples

SYS_GUID Example

Create a simple table and insert a row. In order to display the GUID, convert it to HEX:

CREATE TABLE id_t(a INT, b BINARY(16));
INSERT id_t VALUES(1, SYS_GUID());
SELECT a, HEX(b) FROM id_t;
+------+----------------------------------+
| a    | HEX(b)                           |
+------+----------------------------------+
|    1 | 7CD5B7769DF95CEFE034080020825436 |
+------+----------------------------------+

UUID Example

CREATE TABLE id_t2(a INT, b VARCHAR(36));
INSERT INTO id_t2 VALUES(1, UUID());
SELECT * FROM id_t2;
+------+--------------------------------------+
| a    | b                                    |
+------+--------------------------------------+
|    1 | 15c67225-38f9-483b-8394-02a9e35a9156 |
+------+--------------------------------------+

Last modified: November 12, 2024

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK