MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 5.2  /  Changes in MySQL Connector/ODBC 5.2.3 (2013-01-04, General Availability)

Changes in MySQL Connector/ODBC 5.2.3 (2013-01-04, General Availability)

This release fixes any bugs encountered since Connector/ODBC 5.2.2.

Bugs Fixed

  • Insert operations could fail if the inserted values contained any bit fields, mapped to table columns declared as bit(1):

    Data too long for column 'column_name'

    (Bug #15997361, Bug #67702)

  • Compilation failure was observed for driver/hanlde.c on the Oracle Linux platform. This was due to the use of the function bzero(), which could cause problems on some platforms. This fix replaces the bzero() call with a memset() call. (Bug #15939629)

  • The is_minimum_version function could return an incorrect result in some cases where the difference was in the third component of the release number. (Bug #15926340)

  • An application making extensive use of prepared statements could encounter an error:

    Can't create more than
    max_prepared_stmt_count statements (current value: 16382)

    The issue occurred even if SQLFreeStmt() calls were used. The Prepared_stmt_count value grew until it exceeded the internal limit. A workaround was to disable server-side prepared statements. (Bug #14812778, Bug #67340)

  • The symbols SQLInstallDriverEx, SQLInstallDriverExW, and SQLRemoveDriverW were exported, causing incompatibility with some commercial ODBC packages such as DataDirect ODBC, and making Connector/ODBC dependent on the unixODBC library libodbcinst.so.1. This issue was first observed in Connector/ODBC 5.1.8. (Bug #11766724, Bug #59900)

  • On a 64-bit system, calls to the SQLBindCol function using indicator variables (through the last parameter) could return incorrect results. (Bug #11766437, Bug #59541)