Dear MySQL users,
MySQL Connector/ODBC 5.3.9, a new version of the ODBC driver for
the MySQL database management system, has been released.
The available downloads include both a Unicode driver and an ANSI
driver based on the same modern codebase. Please select the driver type
you need based on the type of your application - Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with any MySQL version from 5.5.
This is the fourth release of the MySQL ODBC driver conforming to the
ODBC 3.8 specification. It contains implementations of key 3.8 features,
including self-identification as a ODBC 3.8 driver, streaming of output
parameters (supported for binary types only), and support of the
SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver
Also, Connector/ODBC 5.3 introduces a GTK+-based setup library
providing a GUI DSN setup dialog on some Unix-based systems, currently
included in the Debian 7/8/9, EL6/OL6, EL7/OL7 (64-bit only), Fedora 24/25/26,
FreeBSD 10/11, SLES 12, Ubuntu 14/16/17 packages. Other new
features in the 5.3 driver are FileDSN and Bookmarks support.
The release is now available in source and binary form for a number of
platforms from our download pages at
For information on installing, please see the documentation at
Changes in MySQL Connector/ODBC 5.3.9 (2017-07-24, General
* Functionality Added or Changed
* Bugs Fixed
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
* The SQLForeignKeys() function returned an empty result
set when the information schema was being used. (Bug
* 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
* Connector/ODBC quit unexpectedly in SQLForeignKeys() when
SQL_MODE was set to ANSI_QUOTES. (Bug #18641824)
Enjoy and thanks for the support!