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

Table 1-3 Features, Behaviors, and Limitations of the Neoview Character Set Configurations
LimitationsFeatures and BehaviorsConfiguration
For this release, the ISO88591 configuration has
these limitations and restrictions:
• Character string literals in an SQL statement are
assumed to be in the ISO8859-1 encoding. An
invalid translation might occur when users
attempt to store a character encoding other than
ISO8859-1, such as the client locale, in a UCS2
column.
• To ensure the correct representation of all
character data sent to UCS2 columns:
— All character data sent to UCS2 columns from
character string literals must be encoded as
ISO8859-1 characters.
— All character data for UCS2 columns that are
bound as parameters are encoded and stored
as UCS2 characters.
• If they want to ensure compatible client locales,
users are required to use only 7-bit ASCII or
ISO8859-1 characters for all SQL identifiers and
user character data. For more information about
compatible client locales, see the troubleshooting
information in Table 5-1 (page 39).
• SQL EMS messages are displayed correctly only
if they are encoded in ISO8859-1. NDCS EMS
messages are displayed correctly only if they are
encoded in 7-bit ASCII.
• SQL string functions assume all characters in
columns defined as ISO88591 columns are
single-byte characters.
• Neoview DB Admin displays only table and
column names that are encoded in ISO8859-1.
• Neoview Management Dashboard displays only
ASCII-formatted characters.
The ISO88591 configuration replicates the
Neoview character set environment for Release
2.2. It allows users to store data encoded in any
character set—including ISO8859-1 through
ISO8859-15 and East Asian multibyte character
sets—in ISO88591 columns.
• The Neoview database stores and retrieves
all client locale character-encoded table
names, column names, and character literals
as if they were encoded in 8-bit ISO8859-1
characters.
• The default column character set definition
is ISO88591.
• Uses binary collation.
• All error messages are sent in the client locale
character encoding.
• The Neoview database assumes that all EMS
event messages are in UTF8 format.
• Neoview platforms with the ISO88591
configuration support the use of Release 2.4,
Release 2.3, and Release 2.2 Neoview ODBC
and JDBC drivers. For more information, see
“Compatibility Between Neoview ODBC and
JDBC Drivers and Neoview Platforms”
(page 19).
ISO88591
For this release, the SJIS configuration has these
limitations and restrictions:
• Character string literals in an SQL statement or
character data bound as parameters are assumed
to be in the MS932 (SJIS) encoding. Attempts to
store any other character encoding in ISO88591
or UCS2 columns are rejected.
• Table names, column names, and character
literals are stored in ISO88591 columns as
SJIS characters using the Microsoft codepage
932 (MS932).
NOTE: Client locales must use
MS932-compliant encoding of SJIS characters
to prevent possible character translation
errors. Client locales that use other encoding
(for example, EUC-JP or standard SJIS) might
generate unrecognizable characters (question
marks) for characters that do not map to
MS932.
SJIS
Neoview Character Set Configurations 17