The default character set of OceanBase AI Database is utf8mb4.
OceanBase AI Database currently supports the following character sets:
binarygbkgb18030utf16utf8mb4/utf8mb3Note
- To support seamless migration, OceanBase AI Database treats
UTF8as a synonym forUTF8MB4in syntax. utf8mb3is an alias forutf8mb4.
- To support seamless migration, OceanBase AI Database treats
latin1gb2312gb18030_2022asciitis620ujiseuckreucjpmscp932utf16lesjisdec8hkscshkscs31big5cp850hp8macromanswe7
The current version of OceanBase AI Database does not support implicit conversion between gb18030 and gb18030_2022. However, you can use the CONVERT function to explicitly convert a gb18030 string's character set to gb18030_2022. This conversion does not go through Unicode and instead preserves the encoding. As shown in the following example, the encoding for '龴' remains 0xFE59 before and after the conversion, unchanged.
obclient [(none)]> SELECT HEX(CONVERT(_gb18030 0xFE59 USING gb18030_2022)), HEX(CONVERT(_gb18030_2022 0xFE59 USING gb18030));
The return result is as follows:
+--------------------------------------------------+--------------------------------------------------+
| HEX(CONVERT(_gb18030 0xFE59 USING gb18030_2022)) | HEX(CONVERT(_gb18030_2022 0xFE59 USING gb18030)) |
+--------------------------------------------------+--------------------------------------------------+
| FE59 | FE59 |
+--------------------------------------------------+--------------------------------------------------+
1 row in set
View available character sets
Run the following SHOW CHARSET statement to view the available character sets.
obclient [(none)]> SHOW CHARSET;
The return result is as follows:
+--------------+---------------------------+-------------------------+--------+
| Charset | Description | Default collation | Maxlen |
+--------------+---------------------------+-------------------------+--------+
| binary | Binary pseudo charset | binary | 1 |
| utf8mb4 | UTF-8 Unicode | utf8mb4_general_ci | 4 |
| gbk | GBK charset | gbk_chinese_ci | 2 |
| utf16 | UTF-16 Unicode | utf16_general_ci | 4 |
| gb18030 | GB18030 charset | gb18030_chinese_ci | 4 |
| latin1 | cp1252 West European | latin1_swedish_ci | 1 |
| gb2312 | GB2312 Simplified Chinese | gb2312_chinese_ci | 2 |
| gb18030_2022 | GB18030-2022 charset | gb18030_2022_chinese_ci | 4 |
| ascii | US ASCII | ascii_general_ci | 1 |
| tis620 | TIS620 Thai | tis620_thai_ci | 1 |
| ujis | EUC-JP Japanese | ujis_japanese_ci | 3 |
| euckr | EUC-KR Korean | euckr_korean_ci | 2 |
| eucjpms | UJIS for Windows Japanese | eucjpms_japanese_ci | 3 |
| cp932 | SJIS for Windows Japanese | cp932_japanese_ci | 2 |
| utf16le | UTF-16LE Unicode | utf16le_general_ci | 4 |
| sjis | SJIS | sjis_japanese_ci | 2 |
| big5 | BIG5 | big5_chinese_ci | 2 |
| hkscs | HKSCS | hkscs_bin | 2 |
| hkscs31 | HKSCS-ISO UNICODE 31 | hkscs31_bin | 2 |
| dec8 | DEC West European | dec8_swedish_ci | 1 |
| cp850 | DOS West European | cp850_general_ci | 1 |
| hp8 | HP West European | hp8_english_ci | 1 |
| macroman | Mac West European | macroman_general_ci | 1 |
| swe7 | 7bit West European | swe7_swedish_ci | 1 |
+--------------+---------------------------+-------------------------+--------+
24 rows in set
Specify a non-default character set
OceanBase AI Database supports specifying a non-default character set for communication with the server. For example, to use the gbk character set, execute the following statement after connecting to the server:
SET NAMES gbk;
Note that the SET NAMES statement does not change the encoding of characters entered by the client. For example, to use SET NAMES to configure the client encoding as gb18030_2022, the client must already be using the gb18030_2022 encoding; otherwise, garbled characters may appear.
/* The client uses the utf8mb4 character set and creates a table named t with the default utf8mb4 character set.*/
obclient> CREATE TABLE t(c VARCHAR(100));
Query OK, 0 rows affected
/* Characters encoded in utf8mb4 are inserted.*/
obclient> INSERT INTO t VALUES ('character set');
Query OK, 1 row affected
/* The character set of the current session has been modified, but the character set actually used by the client remains unchanged.*/
obclient> SET NAMES gb18030_2022;
Query OK, 0 rows affected
/* Still use utf8mb4 encoding to insert characters */
obclient> INSERT INTO t VALUES ('character set');
Query OK, 1 row affected
/* Query data from table t and find garbled characters.*/
obclient> SELECT * FROM t;
+----------+
| c |
+----------+
| �ַ��� |
| �Character |
+----------+
2 rows in set
/* Modify the character set of the current session to utf8mb4 */
obclient> SET NAMES utf8mb4;
Query OK, 0 rows affected
/* Query the data in table t again. The second inserted character is still garbled.*/
obclient> SELECT * FROM t;
+--------------+
| c |
+--------------+
| Character set |
| Yingfu |
+--------------+
2 rows in set