Hexadecimal literal values are written using
X'
or
val
'0x
notation,
where val
val
contains hexadecimal digits
(0..9
, A..F
). Lettercase
of the digits and of any leading X
does not
matter. A leading 0x
is case-sensitive and
cannot be written as 0X
.
Legal hexadecimal literals:
X'01AF'
X'01af'
x'01AF'
x'01af'
0x01AF
0x01af
Illegal hexadecimal literals:
X'0G' (G is not a hexadecimal digit)
0X01AF (0X must be written as 0x)
Values written using
X'
notation
must contain an even number of digits or a syntax error occurs.
To correct the problem, pad the value with a leading zero:
val
'
mysql> SET @s = X'FFF';
ERROR 1064 (42000): You have an error in your SQL syntax;
check the manual that corresponds to your MySQL server
version for the right syntax to use near 'X'FFF''
mysql> SET @s = X'0FFF';
Query OK, 0 rows affected (0.00 sec)
Values written using
0x
notation
that contain an odd number of digits are treated as having an
extra leading val
0
. For example,
0xaaa
is interpreted as
0x0aaa
.
By default, a hexadecimal literal is a binary string, where each pair of hexadecimal digits represents a character:
mysql> SELECT X'4D7953514C', CHARSET(X'4D7953514C');
+---------------+------------------------+
| X'4D7953514C' | CHARSET(X'4D7953514C') |
+---------------+------------------------+
| MySQL | binary |
+---------------+------------------------+
mysql> SELECT 0x5461626c65, CHARSET(0x5461626c65);
+--------------+-----------------------+
| 0x5461626c65 | CHARSET(0x5461626c65) |
+--------------+-----------------------+
| Table | binary |
+--------------+-----------------------+
A hexadecimal literal may have an optional character set
introducer and COLLATE
clause, to designate
it as a string that uses a particular character set and
collation:
[_charset_name] X'val' [COLLATE collation_name]
Examples:
SELECT _latin1 X'4D7953514C';
SELECT _utf8 0x4D7953514C COLLATE utf8_danish_ci;
The examples use
X'
notation,
but val
'0x
notation
permits introducers as well. For information about introducers,
see Section 10.3.8, “Character Set Introducers”.
val
In numeric contexts, MySQL treats a hexadecimal literal like a
BIGINT UNSIGNED
(64-bit unsigned integer). To
ensure numeric treatment of a hexadecimal literal, use it in
numeric context. Ways to do this include adding 0 or using
CAST(... AS UNSIGNED)
. For
example, a hexadecimal literal assigned to a user-defined
variable is a binary string by default. To assign the value as a
number, use it in numeric context:
mysql> SET @v1 = X'41';
mysql> SET @v2 = X'41'+0;
mysql> SET @v3 = CAST(X'41' AS UNSIGNED);
mysql> SELECT @v1, @v2, @v3;
+------+------+------+
| @v1 | @v2 | @v3 |
+------+------+------+
| A | 65 | 65 |
+------+------+------+
An empty hexadecimal value (X''
) evaluates to
a zero-length binary string. Converted to a number, it produces
0:
mysql> SELECT CHARSET(X''), LENGTH(X'');
+--------------+-------------+
| CHARSET(X'') | LENGTH(X'') |
+--------------+-------------+
| binary | 0 |
+--------------+-------------+
mysql> SELECT X''+0;
+-------+
| X''+0 |
+-------+
| 0 |
+-------+
The X'
notation is based on standard SQL. The val
'0x
notation is based on ODBC, for which hexadecimal strings are
often used to supply values for
BLOB
columns.
To convert a string or a number to a string in hexadecimal
format, use the HEX()
function:
mysql> SELECT HEX('cat');
+------------+
| HEX('cat') |
+------------+
| 636174 |
+------------+
mysql> SELECT X'636174';
+-----------+
| X'636174' |
+-----------+
| cat |
+-----------+