MySQL Connector/ODBC Release Notes
The TLSv1.0 and TLSv1.1 connection protocols are now deprecated and support for them is subject to removal in a future Connector/ODBC version.
Additionally, a NO_TLS_1_3 connection option was added. (WL #14543)
Deprecated the NO_I_S
connection option, an
option to get metadata without the information_schema by using
SHOW statements. Setting NO_I_S=1
with
SQLConnect() or SQLDriverConnect() now return
SQL_SUCCESS_WITH_INFO instead of SQL_SUCCESS, and they a
deprecation warning retrievable by SQLGetDiagRec().
(WL #14586)
Applications that use Connector/ODBC now can define query attribute metadata on a per-query basis, without the use of workarounds such as specially formatted comments included in query strings. (WL #14217)
Added the ability to connect to MySQL server accounts that use
the authentication_kerberos
plugin, including
support for user-less and password-less Kerberos
authentications. Connector/ODBC utilizes the MySQL client library for
this functionality.
(WL #14441)
Fixed help
(documentation) links in the ODBC
Driver GUI.
(Bug #32880421)
Improved Access/VB6 query attribute handling. (Bug #32813838)
Attempting to update a row with an existing unique key would not emit a diagnostic error that reported the problem, such as "Duplicate Entry". (Bug #32763378, Bug #103287)
Systems with both GTK versions 2 and 3 could cause the UnixGUI to unexpectedly halt when using the MySQL GUI module. Now, separate GTK modules exist for each version as the two can't co-exist in the same process. (Bug #32623180)
A buffer overrun inside SQLColumns() caused Connector/ODBC to unexpectedly halt; memory management was optimized to prevent this problem.
A workaround was to either use the NO_I_S=1
connection option or enable "Don't use INFORMATION_SCHEMA for
metadata" from the ODBC Data Source Administrator.
(Bug #32612467, Bug #102891)
Fixed insert_params() code to use the __LOCALE_SET and __LOCALE_RESTORE macros rather than setlocale directly. (Bug #32610685, Bug #102871)
Setting NO_CACHE=1
in the ODBC connection
string would cause function errors to go undetected.
(Bug #27499789, Bug #89542)