A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

Binary packages as disk images with installers are now available for Mac OS X.

Binary packages for Sun Solaris are now available as PKG packages.

There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

Incompatible Change: The FLAG_DEBUG option was removed.

MySQL Connector/ODBC now supports batched statements. To enable cached statement support, you must switch enable the batched statement option (FLAG_MULTI_STATEMENTS, 67108864, or Allow multiple statements within a GUI configuration). Be aware that batched statements create an increased chance of SQL injection attacks and you must ensure that your application protects against this scenario. (Bug #7445)

The TRACE and TRACEFILE DSN options have been removed. Use the ODBC driver manager trace options instead.

When connecting to a specific database when using a DSN, the system tables from the mysql database are no longer also available. Previously, tables from the mysql database (catalog) were listed as SYSTEM TABLES by SQLTables() even when a different catalog was being queried. (Bug #28662)

The SQL_ATTR_ROW_BIND_OFFSET_PTR is now supported for row bind offsets. (Bug #6741)

Installed for Mac OS X has been re-instated. The installer registers the driver at a system (not user) level and makes it possible to create both user and system DSNs using the MySQL Connector/ODBC driver. The installer also fixes the situation where the necessary drivers would bge installed local to the user, not globally. (Bug #15326, Bug #10444)

DATETIME column types would return FALSE in place of SQL_SUCCESS when requesting the column type information. (Bug #28657)

The SQL_DATA_TYPE column in SQLColumns() results did not report the correct value for date and time types.

The wrong value for DECIMAL_DIGITS in SQLColumns() was reported for FLOAT and DOUBLE fields, as well as the wrong value for the scale parameter to SQLDescribeCol(), and the SQL_DESC_SCALE attribute from SQLColAttribute().

Binary packages for Sun Solaris are now available as PKG packages.

Binary packages as disk images with installers are now available for Mac OS X.

The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

SQLConnect() and SQLDriverConnect() were rewritten to eliminate duplicate code and ensure all options were supported using both connection methods. SQLDriverConnect() now only requires the setup library to be present when the call requires it.

The wrong value for SQL_DESC_TYPE was returned for date and time types.

The value for SQL_DESC_FIXED_PREC_SCALE was not returned correctly for values in MySQL 5.0 and later.

The SQL_DATETIME_SUB column in SQLColumns() was not correctly set for date and time types.

The wrong value from SQL_DESC_LITERAL_SUFFIX was returned for binary fields.

The SQL_COLUMN_TYPE, SQL_COLUMN_DISPLAY and SQL_COLUMN_PRECISION values would be returned incorrectly by SQLColumns(), SQLDescribeCol() and SQLColAttribute() when accessing character columns, especially those generated through concat(). The lengths returned should now conform to the ODBC specification. The FLAG_FIELD_LENGTH option no longer has any affect on the results returned. (Bug #27862)

The SQLColumns() function could return incorrect information about TIMESTAMP columns, indicating that the field was not nullable. (Bug #14414)

Obtaining the length of a column when using a character set for the connection of utf8 would result in the length being returned incorrectly. (Bug #19345)

Getting table metadata (through the SQLColumns() would fail, returning a bad table definition to calling applications. (Bug #29888)

When using a table with multiple TIMESTAMP columns, the final TIMESTAMP column within the table definition would not be updatable. Note that there is still a limitation in MySQL server regarding multiple TIMESTAMP columns. (Bug #30081)

References: See also Bug #9927.

Fixed an issue where the myodbc3i would update the user ODBC configuration file (~/Library/ODBC/odbcinst.ini) instead of the system /Library/ODBC/odbcinst.ini. This was caused because myodbc3i was not honoring the s and u modifiers for the -d command-line option. (Bug #29964)

BIT(n) columns are now treated as SQL_BIT data where n = 1 and binary data where n > 1.

There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

The SQLColumns() function could return incorrect information about AUTO_INCREMENT columns, indicating that the field was not nullable. (Bug #14407)

A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.