HEX

Returns the hexadecimal representation of numeric, string, or binary data.

Note

Beginning with version 8.5, the way HEX() calculates the values of real and decimal numbers is changed to be more in line with how MySQL HEX() works. Existing implementations of HEX() will return updated values.

Syntax

HEX (expression)

Arguments

  • expression: any valid expression. This can be a column name, literal, or the return value of another function.

Return Type

Upper-case hexadecimal string.

Examples

SELECT HEX(1234);
+-----------+
| HEX(1234) |
+-----------+
| 4D2       |
+-----------+
SELECT HEX('1234');
+-------------+
| HEX('1234') |
+-------------+
| 31323334    |
+-------------+
SELECT HEX('ohai');
+-------------+
| HEX('ohai') |
+-------------+
| 6F686169    |
+-------------+

Note

This function operates on the binary representation of the given argument. That is why the result of hex(1234) and hex('1234') yield different values. This also means that the output of hex( number ) cannot be fed directly into UNHEX to get back the literal number 1234.

Warning

Deprecation Notice

String functions, such as CONCAT, LENGTH, SUBSTR, and HEX, previously operated on the JSON representation of a vector, interpreted as a string. This behavior is deprecated. In the 8.7 release, string functions operate on the binary representation of a vector.

If you truly intend to use a string function on the JSON string representation of a vector, you can write code in the following way so that it will run the same way before and after this behavior change.

Suppose that vec is a vector-type value and stringfunc is any string function and you have expression:

stringfunc(vec)

you can change it to:

stringfunc(vec :> json)

Last modified: June 6, 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