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. SeePAM Pluggable Authentication, andWindows Pluggable Authentication. These capabilities result from linking the Connector/ODBC binaries against the MySQL 5.5.16libmysqlclientrather than the MySQL 5.1libmysqlclientused previously. The newerlibmysqlclientincludes the client-side support needed for the server-side PAM and Windows authentication plugins.

Some catalog functions (such asSQLColumns(),SQLStatistics(), andSQLPrimaryKeys()) would only return one row, when called after pre-execution failed. (Bug #12824839)

The CLI installer scriptmysqlodbc-installerwas missing documentation about how to configure the optional data source parameters. (Bug #12810058)

TheInstall.batscript contained leftover3.51information, and did not properly install the5.1Connector/ODBC connector. (Bug #12781039)

With the optioncharset=cp1251specified in the connection string, the results could be returned asCP1251or asUTF8depending on the query. For example, these queries could give results in different code pages:

select if(1=1,'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, wheresqlwcharchrmight read oneSQLWCHARafter the end of a string. (Bug #61586)

SQLExecutewould returnSQL_SUCCESS_WITH_INFOinstead ofSQL_ERROR, when column parameter binding was enabled. (Bug #59772)

The Connector/ODBC driver did not callmysql_thread_end()when a thread ended, which caused error messages like:Error in my_thread_global_end(): 1 threads didn't exit. (Bug #57727)

当使用连接器/ODBC to fetch data, if anet_write_timeoutcondition occurred, the operation returned the standard "end of data" status, rather than an error. (Bug #39878)

MS Access fields withVARCHAR NOT NULLcolumns could not be altered. (Bug #31067)