Neoview Character Sets Administrator's Guide (R2.4, R2.5)

Table 1-3 Features, Behaviors, and Limitations of the Neoview Character Set Configurations
(continued)
LimitationsFeatures and BehaviorsConfiguration
• Neoview platforms with the SJIS
configuration require Release 2.4 or Release
2.3 Neoview ODBC and JDBC drivers. If you
connect a Release 2.2 driver to a Release 2.4
Neoview platform with the SJIS
configuration, the connection fails and a
connection error is generated. For more
information, see “Compatibility Between
Neoview ODBC and JDBC Drivers and
Neoview Platforms” (page 19).
• Compatible data from EUC-JP or UTF8
character sets is translated to SJIS.
• The default column character set definition
is ISO88591.
• The size of an ISO88591 column indicates the
number of bytes in the column, whether or
not the column contains SJIS characters.
• Uses binary collation, which for SJIS
characters is also JIS collation.
• All EMS messages are sent in UTF8 format.
SJIS
For this release, the Unicode configuration has these
limitations and restrictions:
• To ensure that ODBC client applications can
query tables across multiple client locales, use
7-bit ASCII characters in table and column
names.
• Supports the character sets EUC-JP, KS-Code,
BIG5, GB2312, GB18030, GBK, UTF8, and
UTF16 from client locales. Multibyte client
locale character encoding is converted to
UTF16 encoding when it is stored in UCS2
columns in the Neoview database.
• Neoview platforms with the Unicode
configuration require Release 2.4 or Release
2.3 Neoview ODBC and JDBC drivers. If you
connect a Release 2.2 driver to a Release 2.4
Neoview platform with the Unicode
configuration, the connection fails and a
connection error is generated. For more
information, see “Compatibility Between
Neoview ODBC and JDBC Drivers and
Neoview Platforms” (page 19).
• The default column character set definition
is UCS2.
• User data is encoded in UTF16 for UCS2
columns and UTF8 for ISO88591 columns.
• SQL string functions operate on Unicode
characters in UCS2 columns.
Supplementary-plane characters from
GB18030, which use surrogate pairs, are not
supported by the SQL string functions. SQL
string functions that operate on surrogate
pair characters assume they consist of two
UCS2-encoded characters that comprise four
bytes.
• The size of the character column indicates
the number of 16-bit Unicode characters in a
UCS2 column.
• Table and column names provided in SQL
statements are stored in ISO88591 columns
as UTF8 characters.
• Uses binary collation.
• All EMS messages are sent in UTF8 format.
Unicode
18 Introduction to Neoview Character Sets