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

How Character Encoding Is Implemented in the Neoview JDBC Driver
The Neoview JDBC driver, which uses the Java runtime environment to perform character set
translation, automatically enables or disables translation between client locale and database
encoding based on the Neoview character set configuration of the Neoview platform.
Table C-6 (page 54) describes the translation behavior of the Neoview JDBC driver for the three
Neoview character set configurations.
Table C-6 Character Set Translation Behavior of the Neoview JDBC Driver
Unicode ConfigurationSJIS ConfigurationISO88591 Configuration
Pass-through mode is always disabled
and translation is active.
Pass-through mode is always
disabled and translation is active.
Pass-through mode is enabled and
translation is not active.
NOTE: Even when pass-through mode is enabled in the ISO88591 configuration, all character
data received from client locales and the Neoview database is automatically converted to UTF16
for use with Java String objects by the Neoview JDBC driver, then converted back to its original
encoding on its way to the Neoview database or a client locale.
You can use the replacementString property to specify the string used for character
replacement during character set decoding errors. The replacementString property should
be used only when reading data from the server. Malformed data is rejected when an attempt
is made to insert it. The default value is a question mark.
54 Configuring Neoview Client Applications