Neoview Character Sets Administrator's Guide (R2.4, R2.5)
hexadecimal values as parameters untranslated to the Neoview database. If the Neoview
database attempts to match the hexadecimal values of SJIS characters with the same Unicode
code point value from both sources, they will not match.
• The ODBC driver manager sends the Neoview ODBC driver an SQL statement that contains
both SJIS MS932-encoded character string literals and character values as parameters that
have the same original hexadecimal values. The Neoview ODBC driver converts the regular
character string literals to UTF8 but leaves the character values sent as parameters
untranslated. Again, when the Neoview database compares SJIS MS932-encoded literals
that the driver converted to UTF8 to the untranslated character values, a SJIS character
mismatch occurs.
SJIS character mismatches are confined to SELECT, INSERT UPDATE, and INSERT DELETE
statements with a WHERE clause (predicate) that searches for SJIS character value matches. The
SQL statement is usually reported to the client as having succeeded with no data found.
How to Prevent SQL-Side SJIS Character Mismatches
When using the SJIS configuration with an ODBC connection, SQL-side SJIS character mismatches
can occur in either of the two scenarios described in “SQL-Side SJIS Character Mismatch Scenarios”
(page 43).
To prevent SQL-side SJIS character mismatches from occurring, always send the SJIS character
data in parameters when using an ODBC connection. Do not enclose them in SQL statement
character string literals.
44 Troubleshooting Guidelines for Neoview Character Sets Users