-
+
Localization>
|
SQL_ASCII
- English
+ unspecified (see text)
+ any>
1
UTF8
Unicode, 8-bit
all>
- 1-3
+ 1-4
Unicode>
|
JDBC driver does not support MULE_INTERNAL>, LATIN6>,
LATIN8>, and LATIN10>.
+
+ The SQL_ASCII> setting behaves considerably differently
+ from the other settings. When the server character set is
+ SQL_ASCII>, the server interprets byte values 0-127
+ according to the ASCII standard, while byte values 128-255 are taken
+ as uninterpreted characters. No encoding conversion will be done when
+ the setting is SQL_ASCII>. Thus, this setting is not so
+ much a declaration that a specific encoding is in use, as a declaration
+ of ignorance about the encoding. In most cases, if you are
+ working with any non-ASCII data, it is unwise to use the
+ SQL_ASCII> setting, because
+
PostgreSQL will be unable to help you by
+ converting or validating non-ASCII characters.
+
|
SQL_ASCII
- SQL_ASCII,
- MULE_INTERNAL,
- UTF8
+ any (no conversion will be performed)
|
- To enable the automatic character set conversion, you have to
+ To enable automatic character set conversion, you have to
tell
PostgreSQL the character set
(encoding) you would like to use in the client. There are several
ways to accomplish this:
hexadecimal byte values in parentheses, e.g.,
(826C).
+
+ If the client character set is defined as SQL_ASCII>,
+ encoding conversion is disabled, regardless of the server's character
+ set. Just as for the server, use of SQL_ASCII> is unwise
+ unless you are working with all-ASCII data.
+