HP Integrity NonStop H-Series - Manual (Page 16)

The following are the considerations and limitations for the Windows Unicode driver:
•
You cannot execute DDL statements with character set qualifiers _UCS2 or N.
•
Prefix _UCS2 or N to the string literal for the following columns to execute DML statements:
CHAR CHARACTER SET UCS2 column ◦
◦ NCHAR column — the default NATIONAL character set is UCS2
◦ VARCHAR CHARACTER SET UCS2 column
◦ NCHAR VARYING column — the default NATIONAL character set is UCS2
For example,
insert into CAT.SCH.TAB (unicodechar_col) values (_UCS2'abcd');
•
The driver does not support KANJI and KSC5601 as NATIONAL character set. Prefix _kanji
or _ksc5601 to the string literal for NCHAR column if SQL/MX is installed with KANJI and
KSC5601 as NATIONAL character set.
•
SQL statements and SQLBindParameter values must be in UTF-16 format.
•
The driver considers C variable of type SQL_C_DEFAULT as SQL_C_CHAR instead of
SQL_C_WCHAR to match with the SQL data type of the column or parameter.
•
Consider the following byte length for IN or OUT WCHAR parameter buffer length:
Number of characters * 2 for double byte Unicode characters ◦
◦ Number of characters * 4 for supplementary Unicode characters
•
When the trace is on, the Unicode characters in the SQL statements may not get displayed
properly in the log file.
16 Overview