MySQL Connector/ODBC 5.2.6 has been released

[Kent Boortz]

Dear MySQL users,

MySQL Connector/ODBC 5.2.6, 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 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 since 4.1 (It will not work with 4.0 or
earlier releases.)

The release is now available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/connector/odbc/5.2.html

MySQL Connector/ODBC 5.2.6 will also be available for downloads via the
Oracle Software Delivery Cloud in approximately 1-2 weeks.

For information on installing, please see the documentation at

http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-installation.html

Enjoy!

The MySQL Connectors team at Oracle


==============================================================================

Changes in MySQL Connector/ODBC 5.2.6 

Functionality Added or Changed

  * Added a lock in the ENV structure against simultaneous accesses to
    an environment handle's connection list, in order to avoid memory
    access issues that might occur when multiple threads share the same
    environment handle. (Bug #17240611, Bug #69864)

Bugs Fixed

  * Memory leaks occurred in SQLPrepare() and SQLExecDirect() when
    SQLBindParamater was used on the SQL statements. This fix frees
    previous results of mysql_stmt_result_metadata() in order to prevent
    the memory leaks. (Bug #17400483, Bug #70113)

  * The exit condition for a for loop in stringutil.c is changed to
    avoid a possible out-of-bounds error and the associated reports by
    Valgrind. (Bug #17397596, Bug #64105)

  * Microsoft Visual Studio 2010 crashed when reading rows from any
    table in Server Explorer with connections to DSNs made by
    Connector/ODBC. (Bug #17304031, Bug #69950)

  * When SQL TIME data was converted to the C data type of TIMESTAMP, if
    the value of the hour field is greater than 24, the date fields did
    not get set to the current date and the fraction field for seconds
    did not get set to zero as required by the ODBC specifications.
    (Bug #17016839, Bug #69545)

  * When trying to create a linked server in Micrsoft SQL Server 2008 to
    a MySQL server set up with Connector/ODBC as a DSN, the Microsoft
    SQL Server (if it is a 64-bit version) crashed or the linked server
    suffered a catastrophic failure (if a 32-bit version of the
    Microsoft SQL Server is used). (Bug #16604346, Bug #63386)

  * When reading TIME column data using the SQLGetData method into the
    SQL_C_TYPE_TIME datatype, errors occured when the time string
    contained more than 6-digits (e.g., 120:53:44).
    (Bug #16176981, Bug #67793)

  * When called after SQLPrepare, the funciton SQLMoreResults returned
    SQL_ERROR, instead of SQL_NO_DATA as required by the ODBC
    specification. (Bug #16101282, Bug #67920)

  * Connector/ODBC used the ";" character instead of a null byte ("\0")
    to terminate keyword-value pairs in attribute strings.
    (Bug #15940689, Bug #66548)

  * When using the Unicode-enabled version of the Connector/ODBC driver
    to connect to any MySQL server of version 5.5.2 or older, all
    statements failed with the error message .Server does not support
    4-byte encoded UTF8 characters.. (Bug #14838690, Bug #67428)

  * The configured values of a DSN's parameters overrode the values
    provided through the connection string, instead of the other way
    round. (Bug #11760574, Bug #52996)

Built against the MySQL server 5.6.14 client library.

Kent Boortz, Release Staff Engineer
Oracle, the MySQL team, www.mysql.com