MySQL Connector/ODBC versions

v5.3.6 [Apr 22, 2014]
-Security Fix: The linked OpenSSL library for Connector/ODBC Commercial 5.3.6 has been updated from version 1.0.1m to version 1.0.1q. Versions of OpenSSL prior to 1.0.1q are reported to be vulnerable to CVE-2015-3195.
- Two new option parameters, DISABLE_SSL_DEFAULT and SSL_ENFORCE, have been introduced for specifying whether the default requirement to use SSL connections is to be followed. See Connector/ODBC Option Parameters for details.

v5.2.7 [Jul 4, 2012]
Functionality Added or Changed
--The new connection option can_handle_exp_pwd indicates that your application includes error-handling logic to deal with the error code for an expired password. See Connector/ODBC Connection Parameters for the details of this connection option and the associated SQL state and native error code. See ALTER USER Syntax for details about password expiration for MySQL server accounts.
--This option is added to the Windows GUI, through a checkbox Can Handle Expired Password on the Connection tab of the Details dialog.
--The following reserved words were added to the list returned by the SQLGetInfo() ODBC function, for compatibility with the latest MySQL 5.6 syntax:
-GET
-IO_AFTER_GTIDS
-IO_BEFORE_GTIDS
-MASTER_BIND
-ONE_SHOT
-PARTITION
-SQL_AFTER_GTIDS
-SQL_BEFORE_GTIDS
Bugs Fixed
--When a column with type TINYTEXT, TEXT, MEDIUMTEXT, or LONGTEXT was retrieved from a table with a binary collation, the text fields were converted to a hexadecimal representation, even though these values were not really BLOBs. The unnecessary conversion could expand the data, causing overflow problems when storing the result values.

v5.1.9 [Mar 3, 2008]
Functionality Added or Changed
A new connection option, prefetch, allows applications to scroll through large query result sets, N records at a time. See Section 21.1.4.2, “Connector/ODBC Connection Parameters” for details.
Bugs Fixed
The SQLTables() function did not return the catalog correctly if the wildcard or SQL_ALL_CATALOGS was used. (Bug #13914518)
The fraction member in SQL_TIMESTAMP_STRUCT was always set to 0 when a timestamp was retrieved using SQLGetData(). The fix causes the fraction member to be correctly set, with a value representing nanoseconds. This issue did not occur when a result was retrieved as a string (SQLGetData() with SQL_C_CHAR). (Bug #12767740, Bug #60646)
Fractional seconds part of timestamp was ignored in prepared statements that use SQLBindParameter and SQL_C_TIMESTAMP type. For example, a prepared query comparing two timestamp values that only differed in the fractional part would consider the values identical. (Bug #12767761, Bug #60648)
On Windows platforms, some memory was leaked on each connection attempt due to an incorrect response to a SQLGetDiagRec() call. (Bug #11766029, Bug #59059)