The MaxDB ODBC driver supports UNICODE. Two ODBC drivers are available as of versions 7.4.03.32 / 7.5.00.11:
· ASCII version; always linked to the database kernel via ASCII: sqlod32 (Microsoft Windows) or libsqlod (UNIX).
· UNICODE version; linked to ASCII database kernels via ASCII and to UNICODE database kernels via UCS2: sqlod32w (Microsoft Windows) or libsqlodw (UNIX)
UNIX/Linux:
The ODBC driver cannot be used at present on platforms where the standard UNICODE type WCHAR_T is defined using four bytes. The database and ODBC driver process UNICODE internally as values that are two bytes long.
Applications that do not need Driver Manager functionality can be linked statically with the ODBC driver.
The functions listed below are also available with the UNICODE version of the ODBC driver, irrespective of whether the data source supports UNICODE or not.
Overview of the functions that are defined in the MaxDB ODBC driver for access to UNICODE data
SQLBrowseConnectW
SQLColAttributesW
SQLColAttributeW
SQLColumnPrivilegesW
SQLColumnsW
SQLConnectW
SQLDataSourcesW
SQLDescribeColW
SQLDriverConnectW
SQLDriversW
SQLErrorW
SQLExecDirectW
SQLForeignKeysW
SQLGetConnectAttrW
SQLGetConnectOptionW
SQLGetCursorNameW
SQLGetDescFieldW
SQLGetDescRecW
SQLGetDiagFieldW
SQLGetDiagRecW
SQLGetInfoW
SQLGetStmtAttrW
SQLGetTypeInfoW
SQLNativeSqlW
SQLPrepareW
SQLPrimaryKeysW
SQLProcedureColumnsW
SQLProceduresW
SQLSetConnectAttrW
SQLSetConnectOptionW
SQLSetCursorNameW
SQLSetDescFieldW
SQLSetStmtAttrW
SQLSpecialColumnsW
SQLStatisticsW
SQLTablePrivilegesW
SQLTablesW