MySQL Connector/ODBC 5.3.6 has been released

Dear MySQL users,

MySQL Connector/ODBC 5.3.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 the 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 from 5.5 onward.

This is the third release of the MySQL ODBC driver conforming to the
ODBC 3.8 specification. It contains implementations of key 3.8 features,
including 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).

Also, Connector/ODBC 5.3 introduces a GTK+-based setup library
providing a GUI DSN setup dialog on some Unix-based systems, currently
included in the Oracle Linux 6 and Debian 6 binary packages. Other new
features in the 5.3 driver are FileDSN and Bookmarks support.

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.3.html

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.3.6 (2016-03-17)

    Security Notes

      * Security Fix: The linked OpenSSL library for
        Connector/ODBC Commercial 5.3.6 has been updated from
        version 1.0.1m to version 1.0.1q. Versions of OpenSSL
        prior to 1.0.1q are reported to be vulnerable to
        CVE-2015-3195
        (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3195).
        This change does not affect the Oracle-produced MySQL
        Community build of Connector/ODBC 5.3.6, which uses the
        yaSSL library instead. (CVE-2015-3195)

    Functionality Added or Changed

      * Two new option parameters, DISABLE_SSL_DEFAULT and
        SSL_ENFORCE, have been introduced for specifying whether
        the default requirement to use SSL connections is to be
        followed. See Connector/ODBC Option Parameters
        (http://dev.mysql.com/doc/connector-odbc/en/connector-odb 
<http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html#codbc-dsn-option-flags>
     	c 
<http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html#codbc-dsn-option-flags>-configuration-connection-parameters.html#codbc-dsn-opti 
<http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html#codbc-dsn-option-flags>
	on-flags 
<http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html#codbc-dsn-option-flags>) for details. (Bug #21027928)

    Bugs Fixed

      * The function MySQLGetPrivateProfileStringW() used
        malloc() to allocate memory and then xfree() to free the
        allocated memory for a returned value. That caused some
        issues when certain third-party versions of MySQL client
        library (like MariaDB 10.x) was used. The issues have
        been fixed by replacing malloc() with my_malloc(). (Bug
        #21074676, Bug #76984)

      * Attempt to build Connector/ODBC from source on a Linux
        platform against the client library and header files
        shipped with MySQL server 5.7.6 or newer failed. It was
        due to the changes made to the client library and the
        header files, to which Connector/ODBC has now been
        adapted. (Bug #20685833)

      * An application that used ActiveX Data Objects (ADO) and
        the Connector/ODBC ANSI driver hung after trying to write
        French characters to a database that used the UTF-8
        character set. (Bug #20526062)

      * Calling the SQLGetDiagField function with the
        DiagIdentifier SQL_DIAG_ROW_COUNT always returned "0,"
        even if there were updated, deleted, or modified rows.
        (Bug #16920750)

      * Because Connector/ODBC did not parse comments properly,
        the parameter markers embedded in comments caused the
        complaint that SQLBindParameter was not used for all
        parameters. (Bug #16613308, Bug #53891)


On behalf on the MySQL RE Team.