MX Release 3.2.1 (H06.26+, J06.15+)

◦

◦ SQLGetConfigMode

• SQLBulkOperations

• SQLFetchScroll - supported for SQL_FETCH_NEXT attribute only

• SQLSetScrollOption

Data Types

This release of MXCS does not support the following ODBC data types. For more information about

data types, see ODBC Data Types.

• BIT

• TINYINT and TINYINT UNSIGNED

• BINARY

• VARBINARY

• LONG VARBINARY

Unsupported Functionalities

The OSS ODBC/MX Client Driver does not support the following functionalities:

• Windows-specific APIs that are used for driver installation and driver configuration.

• Dynamic DLL loading while loading OSS ODBC/MX Client Driver, other ODBC Drivers to

external data sources (for example, Oracle or SQLServer).

• Wide character support.

• Windows-styled exception handling.

• Asynchronous semantics. All calls are implemented synchronously. This implies that SQLCancel

can only be invoked on a statement handle after returning from the last invocation on the

handle, not when an operation is running. For example, a runaway query cannot be stopped

by the client application.

• Cursor library.

• Translate library.

• Applications that use windows-specific function class or methods.

• Module file caching(MFC).

Restricted ODBC API Functions

SQLBindParameter

The SQLBindParameter function has these restrictions:

• SQL_DEFAULT_PARAM is not supported for the pcbValue argument.

• The SQL_LEN_DATA_AT_EXEC(length) macro is not supported for the pcbValue argument.

SQLPutData

The SQLPutData function can send data in parts only for the SQL_LONGVARCHAR data type. For

all other data types, only the latest value in the rgbValue argument is used.

22 ODBC/MX Client Overview