Gbase 8C - SQL reference 4 character set support

1. 1. Character set support
      1. Supported character sets

name	describe	Language	Whether the server side ？	ICU？	byte / character	Alias
BIG5	Big Five	Traditional Chinese	no	no	1-2	WIN950, Windows950
EUC_CN	Expand UNIX code - China	Simplified Chinese	yes	yes	1-3
EUC_JP	Expand UNIX code - Japan	Japanese	yes	yes	1-3
EUC_JIS_2004	Expand UNIX code - Japan , JIS X 0213	Japanese	yes	no	1-3
EUC_KR	Expand UNIX code - South Korea	Korean	yes	yes	1-3
EUC_TW	Expand UNIX code - Taiwan	Traditional Chinese , Taiwanese	yes	yes	1-3
GB18030	National standard	chinese	yes	no	1-4
GBK	Expand national standards	Simplified Chinese	no	no	1-2	WIN936, Windows936
ISO_8859_5	ISO 8859-5, ECMA 113	Latin / Cyrillic	yes	yes	1
ISO_8859_6	ISO 8859-6, ECMA 114	Latin / The Arabic language	yes	yes	1
ISO_8859_7	ISO 8859-7, ECMA 118	Latin / Greek	yes	yes	1
ISO_8859_8	ISO 8859-8, ECMA 121	Latin / Hebrew	yes	yes	1
JOHAB	JOHAB	Korean	no	no	1-3
KOI8R	KOI8-R	Cyrillic （ Russian ）	yes	yes	1	KOI8
KOI8U	KOI8-U	Cyrillic （ Ukrainian ）	yes	yes	1
LATIN1	ISO 8859-1, ECMA 94	Western Europe	yes	yes	1	ISO88591
LATIN2	ISO 8859-2, ECMA 94	Central Europe	yes	yes	1	ISO88592
LATIN3	ISO 8859-3, ECMA 94	Southern Europe	yes	yes	1	ISO88593
LATIN4	ISO 8859-4, ECMA 94	Nordic	yes	yes	1	ISO88594
LATIN5	ISO 8859-9, ECMA 128	Turkish language	yes	yes	1	ISO88599
LATIN6	ISO 8859-10, ECMA 144	Germanic	yes	yes	1	ISO885910
LATIN7	ISO 8859-13	the Baltic	yes	yes	1	ISO885913
LATIN8	ISO 8859-14	Celtic	yes	yes	1	ISO885914
LATIN9	ISO 8859-15	With Europa and accent LATIN1	yes	yes	1	ISO885915
LATIN10	ISO 8859-16, ASRO SR 14111	romanian	yes	no	1	ISO885916
MULE_INTERNAL	Mule Internal encoding	Multilingual editor	yes	no	1-4
SJIS	Shift JIS	Japanese	no	no	1-2	Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004	Shift JIS, JIS X 0213	Japanese	no	no	1-2
SQL_ASCII	Not specified （ See text ）	arbitrarily	yes	no	1
UHC	Unified Korean code	Korean	no	no	1-2	WIN949, Windows949
UTF8	Unicode, 8-bit	all	yes	yes	1-4	Unicode
WIN866	Windows CP866	Cyrillic	yes	yes	1	ALT
WIN874	Windows CP874	Thai,	yes	no	1
WIN1250	Windows CP1250	Central Europe	yes	yes	1
WIN1251	Windows CP1251	Cyrillic	yes	yes	1	WIN
WIN1252	Windows CP1252	Western Europe	yes	yes	1
WIN1253	Windows CP1253	Greek	yes	yes	1
WIN1254	Windows CP1254	Turkish language	yes	yes	1
WIN1255	Windows CP1255	Hebrew	yes	yes	1
WIN1256	Windows CP1256	The Arabic language	yes	yes	1
WIN1257	Windows CP1257	the Baltic	yes	yes	1
WIN1258	Windows CP1258	Vietnamese	yes	yes	1	ABC, TCVN, TCVN5712, VSCII

1. 1. 1. Set character set

initdb Define the default character set of the database / code , for example ：

initdb -E GKR

It can be used --encoding Instead of -E. If not given -E perhaps --encoding Options ,initdb Will try to determine the appropriate encoding to use based on the specified or default region .

Use non default character set / When coding , It should be considered compatible with the selected area ：

createdb -E EUC_KR -T template0 --lc-collate=ko_KR.euckr --lc-ctype=ko_KR.euckr korean

Or use SQL Command implementation ：

CREATE DATABASE korean WITH ENCODING 'GB18030' LC_COLLATE='ko_KR.euckr' LC_CTYPE='ko_KR.euckr' TEMPLATE=template0;

Character set of database / The encoding is stored in the system directory pg_database in . have access to gsql -l Options or \l Command to view .

gsql -l

                               List of databases

    Name     | Owner | Encoding |   Collate   |    Ctype    | Access privileges

-------------+-------+----------+-------------+-------------+-------------------

 gbase       | gbase | UTF8     | zh_CN.UTF-8 | zh_CN.UTF-8 |

 korean      | gbase | EUC_KR   | ko_KR.euckr | ko_KR.euckr |

 template0   | gbase | UTF8     | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/gbase         +

             |       |          |             |             | gbase=CTc/gbase

 template1   | gbase | UTF8     | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/gbase         +

             |       |          |             |             | gbase=CTc/gbase

(4 rows)

1. 1. 1. Automatic character set conversion between server and client

Server character set	Available client character sets
BIG5	Coding as a server is not supported
EUC_CN	EUC_CN, MULE_INTERNAL, UTF8
EUC_JP	EUC_JP, MULE_INTERNAL, SJIS, UTF8
EUC_KR	EUC_KR, MULE_INTERNAL, UTF8
EUC_TW	EUC_TW, BIG5, MULE_INTERNAL, UTF8
GB18030	UTF8
GBK	Coding as a server is not supported
ISO_8859_5	ISO_8859_5, KOI8R, MULE_INTERNAL, UTF8, WIN866, WIN1251
ISO_8859_6	ISO_8859_6, UTF8
ISO_8859_7	ISO_8859_7, UTF8
ISO_8859_8	ISO_8859_8, UTF8
JOHAB	JOHAB, UTF8
KOI8R	KOI8R, ISO_8859_5, MULE_INTERNAL, UTF8, WIN866, WIN1251
KOI8U	KOI8U, UTF8
LATIN1	LATIN1, MULE_INTERNAL, UTF8
LATIN2	LATIN2, MULE_INTERNAL, UTF8, WIN1250
LATIN3	LATIN3, MULE_INTERNAL, UTF8
LATIN4	LATIN4, MULE_INTERNAL, UTF8
LATIN5	LATIN5, UTF8
LATIN6	LATIN6, UTF8
LATIN7	LATIN7, UTF8
LATIN8	LATIN8, UTF8
LATIN9	LATIN9, UTF8
LATIN10	LATIN10, UTF8
MULE_INTERNAL	MULE_INTERNAL, BIG5, EUC_CN, EUC_JP, EUC_KR, EUC_TW, ISO_8859_5, KOI8R, LATIN1 to LATIN4, SJIS, WIN866, WIN1250, WIN1251
SJIS	Coding as a server is not supported
SQL_ASCII	arbitrarily （ No conversion will be performed ）
UHC	Coding as a server is not supported
UTF8	All supported encodings
WIN866	WIN866, ISO_8859_5, KOI8R, MULE_INTERNAL, UTF8, WIN1251
WIN874	WIN874, UTF8
WIN1250	WIN1250, LATIN2, MULE_INTERNAL, UTF8
WIN1251	WIN1251, ISO_8859_5, KOI8R, MULE_INTERNAL, UTF8, WIN866
WIN1252	WIN1252, UTF8
WIN1253	WIN1253, UTF8
WIN1254	WIN1254, UTF8
WIN1255	WIN1255, UTF8
WIN1256	WIN1256, UTF8
WIN1257	WIN1257, UTF8
WIN1258	WIN1258, UTF8

Enable automatic character set conversion , You need to inform the database client of the character set used / code ：

1. use gsql Inside \encoding command . for example , Change the code to SJIS：

\encoding SJIS

1. libpq Function control client code is provided in .
2. Use SET client_encoding TO Set client code ：

SET CLIENT_ENCODING TO 'value';

Or use SQL Of SET NAMES：

SET NAMES 'value';

Query the current client code ：

SHOW client_encoding;

Reset to default encoding ：

RESET client_encoding;

1. Use PGCLIENTENCODING. If defined in the client environment PGCLIENTENCODING environment variable , Then the client code will be automatically selected after connecting with the server （ This setting can then be overridden using any of the other methods mentioned above ）.

Use client_encoding Configuration variables . If client_encoding The variable is set , So after establishing a connection with the server , This client code will be automatically selected （ This setting can then be overloaded using the methods mentioned above ）.