Web lists-archives.com

MySQL Connector/ODBC 8.0.13 has been released




Dear MySQL users,

MySQL Connector/ODBC 8.0.13 is a new version in the MySQL
Connector/ODBC 8.0 series, the ODBC driver for the MySQL Server.

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 server version from 5.5.

This release of the MySQL ODBC driver is 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).

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

  https://dev.mysql.com/downloads/connector/odbc/

For information on installing, please see the documentation at

  https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html

Changes in MySQL Connector/ODBC 8.0.13 (2018-10-22, General Availability)

   Functionality Added or Changed

     * Added dynamic libmysql linking support via the
       -DMYSQLCLIENT_STATIC_LINKING:BOOL=TRUE|FALSE option;
       defaults to FALSE to enable dynamic linking.

   Bugs Fixed

     * Fixed column metadata handling with Microsoft Access.
       (Bug #28670725, Bug #91856)

     * The following obsolete options were removed: NO_SCHEMA
       (use NO_CATALOG instead), DISABLE_SSL_DEFAULT (use
       SSLMODE instead), and SSL_ENFORCE (use SSLMODE instead).
       (Bug #28407520)

     * The ODBC Driver returned 0 for the
       SQL_MAX_SCHEMA_NAME_LEN attribute, and now returns 64 as
       the maximum length for a MySQL schema name.
       (Bug #28385722)

     * Because the MySQL ODBC driver ignored the SQL_RD_OFF
       value for the SQL_ATTR_RETRIEVE_DATA attribute, it
       incorrectly kept writing into the data buffers. This led
       to write access violation errors when data was written
       into the buffer when the user application explicitly
       requested not to write there. (Bug #28098219, Bug #91060)

On Behalf of Oracle/MySQL Release Engineering Team,
Kent Boortz

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql