Neoview Character Sets Administrator's Guide (R2.3)

Table 1-3 Features, Behaviors, and Limitations of the Neoview Character Set Configurations
(continued)
LimitationsFeatures and BehaviorsConfiguration
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.
• Certain SQL functions, including string
functions, are not supported in the Unicode
configuration. For information about Neoview
Character Sets support for SQL functions, see
Chapter 3 (page 23).
• 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.
• Requires Release 2.3 Neoview ODBC and
Neoview JDBC drivers. If you connect a
Release 2.2 driver to a Release 2.3 Neoview
platform using the Unicode configuration,
the connection fails and a connection error is
generated. For more information, see
“Compatibility Between Neoview ODBC and
JDBC Drivers and the Neoview Database”
(page 18).
• 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.
Compatibility Between Neoview ODBC and JDBC Drivers and the Neoview
Database
Neoview ODBC drivers and Neoview JDBC drivers can be connected to a network that contains
both Release 2.3 and Release 2.2 Neoview platforms and operate according to these rules:
• Release 2.3 Neoview ODBC and Neoview JDBC drivers are backward compatible with
Release 2.2 Neoview platforms.
• Release 2.2 Neoview ODBC and Neoview JDBC drivers can be connected only to a Release
2.3 Neoview platform that uses the ISO88591 configuration. If you connect Release 2.2 drivers
to a Release 2.3 Neoview platform that uses the SJIS or Unicode configuration, the connection
fails and a connection error is generated. For information about troubleshooting this
connection error, see the Chapter 5 (page 35).
18 Introduction to Neoview Character Sets