Related Documentation Download these Release Notes
PDF (US Ltr) - 399.9Kb
PDF (A4) - 399.5Kb

MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 5.3  /  Changes in MySQL Connector/ODBC 5.3.8 (2017-04-28, General Availability)

Changes in MySQL Connector/ODBC 5.3.8 (2017-04-28, General Availability)

Security Notes

  • The linked OpenSSL library for Connector/ODBC Commercial 5.3.8 has been updated from version 1.0.2j to version 1.0.2k. Versions of OpenSSL prior to 1.0.2k are reported to be vulnerable to CVE-2017-3731, CVE-2017-3732, and CVE-2017-7055.

    This change does not affect the Oracle-produced MySQL Community build of Connector/ODBC 5.3.8, which uses the yaSSL library instead. (Bug #25615448)

Bugs Fixed

  • When error 2006 (MySQL server has gone away) occurred, Connector/ODBC wrongly returned the SQL_NO_DATA error. (Bug #25671389)

  • When the SQL_TIMESTAMP_STRUCT was used, if the date portion of a timestamp was populated but the time portion was uninitialized, queries involving the timestamp would fail with a Date overflow error. With this fix, the uninitialized time value is simply ignored. (Bug #25386024)

  • Several fixes were made to the packaged README file, including the copyright year. (Bug #22858162)

  • Segmentation faults occurred when catalog, column, or table names that were too long were passed as arguments to metadata functions like SQLColumnPrivileges(),SQLColumns(),SQLTablePrivileges() and SQLTables(). With this fix, proper errors are returned in those cases. (Bug #18796005)

  • An assertion error occurred when calling SQLSetDescField() with SQL_DESC_COUNT as FieldIdentifier, irrespective of the record number set. (Bug #18641633)

  • Connector/ODBC quit unexpectedly when a negative column number was passed as an argument for the SQLGetData() method. (Bug #18636600)

  • When server-side prepared statements were enabled, using the prefetch option caused SQL syntax errors to be returned for queries that contained parameter markers. (Bug #17386788)

  • After the attribute SQL_ATTR_MAX_ROWS had been set for a certain statement handler, a new statement handler also had the same value set automatically. The fix makes sure a new statement handler returns all rows by default. (Bug #17259397, Bug #69554)

  • If the NO_INFORMATION_SCHEMA connection option was set, the SQLTables() function did not return the catalog correctly when a wildcard or SQL_ALL_CATALOGS was used in its arguments. (Bug #14005343)

    References: See also: Bug #13914518.