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

client locale character set, SJIS characters, or UTF8 characters, depending on the selected Neoview
character set configuration.
Table 1-1 (page 14) identifies the character set encodings that the Neoview database uses to store
characters in ISO88591 and UCS2 columns for the three Neoview character set configurations.
Table 1-1 Character Sets Stored in ISO88591 and UCS2 Columns for the Neoview Character Set
Configurations
Unicode ConfigurationSJIS ConfigurationISO88591 Configuration
UTF8 charactersSJIS charactersClient locale charactersCharacter set stored in
ISO88591 columns in this
configuration
UCS2 characters• All character data sent to
UCS2 columns in SQL
statement character
string literals must be
encoded and stored as
SJIS characters.
• All character data for
UCS2 columns that is
bound as parameters is
encoded and stored as
UCS2 characters.
• All character data sent to
UCS2 columns in SQL
statement character
string literals must be
encoded and stored as
ISO8859-1 characters.
• All character data for
UCS2 columns that is
bound as parameters is
encoded and stored as
UCS2 characters.
Character set stored in
UCS2 columns in this
configuration
The first row in Table 1-1 (page 14) identifies the character set encoding stored in ISO88591
columns in the three configurations. In the ISO88591 configuration, any supported client locale
character set can be stored in ISO88591 columns. In the SJIS configuration, SJIS characters are
stored. In the Unicode configuration, UTF8 characters are stored in ISO88591 columns. UTF8
characters are also stored in metadata columns that contain table names, view names, column
names, and the SQL test for constraints.
The second row in Table 1-1 (page 14) shows that, for the ISO88591 and SJIS configurations, the
Neoview database encodes and stores character data for UCS2 columns from SQL statement
character string literals differently than it does character data for UCS2 columns sent as
parameters. The Neoview database does this to ensure the correct representation of the stored
data. For the Unicode configuration, all character data for UCS2 columns is encoded and stored
in UCS2 format.
To further illustrate these restrictions on character set encoding for UCS2 columns in the ISO88591
and SJIS configurations, assume an ISO88591 configuration with a client locale that uses
MS932-encoded SJIS characters. Users can store these client locale SJIS characters in UCS2 columns
only if they send them as parameters. However, if they send the SJIS characters in SQL statement
character string literals, the characters are automatically stored in their ISO8859-1 representation,
not as proper SJIS characters.
Table 1-2 (page 15) identifies:
• The default column character set definition for each configuration
• The non-default column character set definition for each configuration
• The default character string literal prefix for each configuration
• The non-default character string literal prefixes for each configuration
14 Introduction to Neoview Character Sets