title | summary | aliases | ||
---|---|---|---|---|
SHOW COLLATION | TiDB SQL Statement Reference |
An overview of the usage of SHOW COLLATION for the TiDB database. |
|
This statement provides a static list of collations, and is included to provide compatibility with MySQL client libraries.
Note:
Results of
SHOW COLLATION
vary when the "new collation framework" is enabled. For new collation framework details, refer to Character Set and Collation.
ShowCollationStmt:
When new collation framework is disabled, only binary collations are displayed.
mysql> SHOW COLLATION;
+-------------+---------+------+---------+----------+---------+
| Collation | Charset | Id | Default | Compiled | Sortlen |
+-------------+---------+------+---------+----------+---------+
| utf8mb4_bin | utf8mb4 | 46 | Yes | Yes | 1 |
| latin1_bin | latin1 | 47 | Yes | Yes | 1 |
| binary | binary | 63 | Yes | Yes | 1 |
| ascii_bin | ascii | 65 | Yes | Yes | 1 |
| utf8_bin | utf8 | 83 | Yes | Yes | 1 |
+-------------+---------+------+---------+----------+---------+
5 rows in set (0.02 sec)
When new collation framework is enabled, utf8_general_ci
and utf8mb4_general_ci
are additionally supported.
mysql> SHOW COLLATION;
+--------------------+---------+------+---------+----------+---------+
| Collation | Charset | Id | Default | Compiled | Sortlen |
+--------------------+---------+------+---------+----------+---------+
| utf8mb4_bin | utf8mb4 | 46 | Yes | Yes | 1 |
| latin1_bin | latin1 | 47 | Yes | Yes | 1 |
| binary | binary | 63 | Yes | Yes | 1 |
| ascii_bin | ascii | 65 | Yes | Yes | 1 |
| utf8_bin | utf8 | 83 | Yes | Yes | 1 |
| utf8_general_ci | utf8 | 33 | | Yes | 1 |
| utf8mb4_general_ci | utf8 | 45 | | Yes | 1 |
+--------------------+---------+------+---------+----------+---------+
7 rows in set (0.02 sec)
The usage of this statement is understood to be fully compatible with MySQL. However, charsets in TiDB may have different default collations compared with MySQL. For details, refer to Compatibility with MySQL. Any other compatibility differences should be reported via an issue on GitHub.