MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 5.2  /  Changes in MySQL Connector/ODBC 5.2.2 (2012-09-20, General Availability)

Changes in MySQL Connector/ODBC 5.2.2 (2012-09-20, General Availability)

This is the first GA release for the Connector/ODBC 5.2.x series. Now the available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Server-side stored procedures are enabled by default.

Functionality Added or Changed

  • The download page now offers choices of a Unicode driver or an ANSI driver. Now users can get an ANSI driver with the combination of high performance and the latest standard-compliant behavior, rather than staying on the older 3.51 codebase.

  • Server-side prepared statements are now enabled by default. To revert to the former behavior, using client-side emulation for prepared statemnts, specify the NO_SSPS option when configuring the DSN. (WL #5849)

  • The implementation of the SQLBindParameter() function was enhanced to support out and inout parameters when calling stored procedures. Designate the bind parameters intended to hold output values from stored procedures using the type specifiers SQL_PARAM_OUTPUT or SQL_PARAM_INPUT_OUTPUT.


    Currently, the support for out and inout parameters does not apply to LONGTEXT and LONGBLOB columns.

    (WL #6116)

Bugs Fixed

  • Improved error handling for bad input data, such as an incorrect SQLSetConnectAttr length. This fix improves reliability in cases such as an ANSI application using a Unicode driver. (Bug #14620420)

  • The string returned by the SQLNativeSql function was not null-terminated as it should be. (Bug #14559721)

  • After executing a stored procedure returning a combination of resultsets and OUT parameters, Connector/ODB would be disconnected from the server. The issue occurred after fetching the result sets and executing a subsequent query. (Bug #14512187)

  • Specifying certain values for the CHARSET option in the connection string could cause a serious error when a query was executed. (Bug #14363601)