Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of MySQL Connector/ODBC 5.1.x before upgrading.

References: See also Bug #34571.

The installer for 64-bit Windows installs both the 32-bit and 64-bit driver. Please note that Microsoft does not yet supply a 64-bit bridge from ADO to ODBC.

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.

SQLForeignKeys uses INFORMATION_SCHEMA when it is available on the server, which enables more complete information to be returned.

Disabled MYSQL_OPT_SSL_VERIFY_SERVER_CERT when using an SSL connection.

Explicit descriptors are implemented. (Bug #32064)

Changed SQL_ATTR_PARAMSET_SIZE to return an error until support for it is implemented.

A full implementation of SQLForeignKeys based on the information available from INFORMATION_SCHEMA in 5.0 and later versions of the server has been implemented.

Specifying a nonexistent database name within the GUI dialog would result in an empty list, not an error. (Bug #33615)

The SSLCIPHER option would be incorrectly recorded within the SSL configuration on Windows. (Bug #33897)

Within the GUI interface, when connecting to a MySQL server on a nonstandard port, the connection test within the GUI would fail. The issue was related to incorrect parsing of numeric values within the DSN when the option was not configured as the last parameter within the DSN. (Bug #33822)

When deleting rows from a static cursor, the cursor position would be incorrectly reported. (Bug #33388)

SQLGetInfo() reported characters for SQL_SPECIAL_CHARACTERS that were not encoded correctly. (Bug #33130)

When accessing column data, FLAG_COLUMN_SIZE_S32 did not limit the octet length or display size reported for fields, causing problems with Microsoft Visual FoxPro.

The list of ODBC functions that could have caused failures in Microsoft software when retrieving the length of LONGBLOB or LONGTEXT columns includes:

Retrieving data from a BLOB column would fail within SQLGetDatawhen the target data type was SQL_C_WCHAR due to incorrect handling of the character buffer. (Bug #32684)

Dynamic cursors on statements with parameters were not supported. (Bug #11846)

Reading a TEXT column that had been used to store UTF8 data would result in the wrong information being returned during a query. (Bug #28617)

Evaluating a simple numeric expression when using the OLEDB for ODBC provider and ADO would return an error, instead of the result. (Bug #10128)

SQLForeignKeys would return an empty string for the schema columns instead of NULL. (Bug #19923)

Renaming an existing DSN entry would create a new entry with the new name without deleting the old entry. (Bug #31165)

Adding or updating a row using SQLSetPos() on a result set with aliased columns would fail. (Bug #6157)