This is a beta release for the Connector/ODBC 5.3.x series. 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—Unicode or ANSI—based on the type of your application. Server-side prepared statements are enabled by default. It is suitable for use with any MySQL version since 4.1 (it will not work with 4.0 or earlier releases.)
This is the second release of the MySQL ODBC driver conforming to the ODBC 3.8 specification. It contains the minimally required implementation of the standard with key ODBC 3.8 features, which include 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 only).
Connector/ODBC 5.3 also introduces a GTK+-based setup library, providing GUI DSN setup dialog on some Unix-based systems. The library is currently included in the Oracle Linux 6 and Debian 6 binary packages. Other new features in the 5.3 series include File DSN and bookmark support.
Keep in mind that this is a beta release and, as with any other pre-production releases, cautions should be taken when installing on production level systems or systems with critical data. Not all of the features planned for the final Connector/ODBC 5.3 release are implemented.
SQL_ATTR_RESET_CONNECTIONconnection attribute, newly introduced in ODBC 3.8. See the ODBC specifications for details. Currently, the connection attribute is supported by the Unicode driver, but not the ANSI driver.
SQLSetStmtAttrresulted in a segmentation fault. (Bug #17714290)
A memory leak occurred when using Connector/ODBC to update the contents of a row. (Bug #17653461, Bug #70662)
A bad memory access occurred in the
my_prepared_stmt.c, when a call was made to a stored procedure with any
INparameters coming after the last
INOUTparameter. (Bug #17640929, Bug #70642)
A memory leak occurred in
SQLConnect()when it was invoked after a call of
SQLSetConnectAttr()that used the parameter
SQL_ATTR_CURRENT_CATALOG. (Bug #17586844)
In ODBCManageDataSourcesQ4, when creating a new DSN with a Unix socket instead of a TCP connection,
NAMED_PIPEwas set to “1” in the created DSN, which caused all connections that used the DSN to fail with the “Wrong or unknown protocol” error. (Bug #17586452)