Only the source code and Windows binaries are available with this release.
The 64-bit MSI installer no longer contains 32-bit and 64-bit builds of the driver, like it did in previous versions. It now only includes 64-bit support.
The binaries for this distribution of Connector/ODBC can now
connect to MySQL server accounts that use the PAM or Windows
Native Authentication Plugins for authentication. See
The PAM Authentication Plugin, and
The Windows Native Authentication Plugin. These
capabilities result from linking the Connector/ODBC binaries
against the MySQL 5.5.16
rather than the MySQL 5.1
previously. The newer
the client-side support needed for the server-side PAM and
Windows authentication plugins.
Some catalog functions (such as
SQLPrimaryKeys()) would only return one row,
when called after pre-execution failed.
The CLI installer script
mysqlodbc-installer was missing
documentation about how to configure the optional data source
Install.bat script contained leftover
3.51 information, and did not properly
5.1 Connector/ODBC connector.
With the option
charset=cp1251 specified in
the connection string, the results could be returned as
CP1251 or as
depending on the query. For example, these queries could give
results in different code pages:
string in cp1251 code page',0) as '
string in cp1251 code page'; select '
string in cp1251 code page' as '
string in cp1251 code page';
(Bug #11765110, Bug #58038)
An off-by-one error, where
SQLWCHAR after the end of a string.
SQLExecute would return
SQL_SUCCESS_WITH_INFO instead of
SQL_ERROR, when column parameter binding was
The Connector/ODBC driver did not call
mysql_thread_end() when a thread
ended, which caused error messages like:
my_thread_global_end(): 1 threads didn't exit.
When using MySQL Connector/ODBC to fetch data, if a
net_write_timeout condition occurred, the
operation returned the standard "end of data" status, rather
than an error.
MS Access fields with
VARCHAR NOT NULL
columns could not be altered.