JDBC, ODBC, the C/C++ Precompiler and Python support UNICODE.
Since Java works with UNICODE strings, it can read and write UNICODE columns.
If you also want to use UNICODE in SQL statements, you must set the unicode CONNECT-property to true. SQL statements are then transferred to the database instance in UTF-16/UCS-2 format. If the transfer package for the SQL statements is not large enough, you can increase its size using database parameter _PACKET_SIZE.
UNICODE is supported in the ODBC driver.
Depending on your operating system, you must take account of the following factors:
Operating System |
|
Windows 2000 |
The ODBC driver only exports the UNICODE and/or Wide functions of the ODBC-API. ANSI functions are mapped to the relevant Wide functions by the Windows Driver Manager . This means that applications can use both the ANSI and the UNICODE functions of the ODBC-API. |
UNIX/Linux |
The
use of the ODBC driver is currently not possible on platforms for which the
standard UNICODE type WCHAR_T is defined with four bytes. The
database and ODBC driver process UNICODE internally as values that are two
bytes long. |
During CONNECT, the C/C++ Precompiler checks whether the database is UNICODE-enabled (Database parameter _UNICODE = YES).
See also: Example 2 (HelloUnicodeDB.cpc) and Working with UNICODE Data
Python 2.*: UNICODE columns can be read and written. UNICODE character strings cannot be used as SQL statements.
Python 1.5.2: UNICODE-type output values are converted to ASCII. If this conversion fails, an error is reported.