Documentation Home
MySQL Connector/ODBC Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 291.7Kb
PDF (A4) - 289.4Kb


MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 5.3  /  Changes in MySQL Connector/ODBC 5.3.9 (2017-07-24, General Availability)

Changes in MySQL Connector/ODBC 5.3.9 (2017-07-24, General Availability)

Security Notes

  • The linked OpenSSL library for MySQL Connector/ODBC 5.3.9 Commercial has been updated to version 1.0.2l.

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

Functionality Added or Changed

  • When compiling Connector/ODBC on Windows platforms, it can now be linked statically (equivalent to the /MT compiler option in Visual Studio) or dynamically (equivalent to the /MD compiler option in Visual Studio) to the Visual C++ runtime. The default option is to link dynamically; if you want to link statically. set the new CMake option, STATIC_MSVCRT, to true.

    Another new CMake option, WITH_NODEFAULTLIB, has been introduced for specifying the Visual C++ runtime you want to link Connector/ODBC to when using mixed link types (that is, when link type to the Visual C++ runtime differs for Connector/ODBC and the MySQL client library it links to).

    See Building Connector/ODBC from a Source Distribution on Windows for details.

Bugs Fixed

  • The SQLForeignKeys() function returned an empty result set when the information schema was being used. (Bug #26388694)

  • Calling SQLExecute() after calling SQLFreeStmt() with the SQL_RESET_PARAMS option resulted in an assertion failure. With this fix, a proper error is now thrown in the situation. (Bug #19148246)

  • A segmentation fault occurred in SQLFetch() when SQL_ATTR_CURSOR_TYPE was set to SQL_CURSOR_DYNAMIC. (Bug #18805392)

  • Connector/ODBC quit unexpectedly in SQLForeignKeys() when SQL_MODE was set to ANSI_QUOTES. (Bug #18641824)