MySQL Connector/ODBC - Connect to a MySQL database server using the ODBC database API

MySQL Connector/ODBC (with MyODBC as acronym) allows you to connect to a MySQL database server using the ODBC database API on all Microsoft Windows and most Unix platforms, including through such applications and programming environments such as Microsoft

Here are some key features of "MySQL Connector ODBC":

￭ Standards compliant
The production-ready version of Connector/ODBC is compliant with the ODBC 2.50 specification, Level 0 (with some Level 1 and 2 features). The stable version, is compliant with the ODBC 3.51 specification, Level 1 (complete Core API and Level 2 features).
￭ Cross-platform
Connector/ODBC is available for Microsoft Windows, as well as many Unix systems (including Linux, Sun Solaris, HP-UX, IBM AIX, and Mac OS X).

What's New in This Release: [ read full changelog ]

· ConfigDSN() returned FALSE when the dialog was cancelled by the user.
· Static cursor was unable to be used through ADO when dynamic cursors were enabled.
· Driver would crash when requesting the current catalog before connecting.
· Catalog data was truncated due to NAME_LEN only allocating a single byte for characters.
· SSL connections could not be established properly. Added the server certificate verification flag.
· Added deprecated SQLSetParam function.
· Recordset-based update fails if blob field is queried.
· Allows dirty reading with SQL_TXN_READ_COMMITTED isolation through ODBC
· Don't cache results and SQLExtendedFetch work badly together.
· SQLFetch or SQLFetchScroll returns negative data length using SQL_C_WCHAR.
· An SQLSTATE of HY000 was returned when a stored procedure was not found, instead of 42000. This caused problems with ADO's adCmdUnknown option.
· Identifiers were quoted incorrectly by SQLColumns().
· Worked around bug in iODBC installer library that made it impossible to create a system DSN, particularly on Mac OS X, where the installer created the /Library/ODBC/*.ini files with insufficient permissions.
· Unresolved symbols "min" and "max" in libmyodbc3.so with gcc 4.2.
· Fixed some incorrect information returned by SQLGetTypeInfo().
· Values bound using the SQL_C_CHAR value type but with numeric parameter type were not correctly escaped.
· The driver reported that it does not support SQLProcedureColumns(), which causes problems for ADO.