Clear text authentication to MySQL servers is now supported by Connector/ODBC. The support is controlled by the new
Enable Cleartext Authentication
connection option (with the flag nameENABLE_CLEARTEXT_PLUGIN
). (Bug #16445091)
A data connection could not be opened in Microsoft Word 2010 for mail merges that attempted to use an ODBC DSN. (Bug #16526604, Bug #63844)
-
The
query_print()
function could cause a serious error on 32-bit systems due to a 32-bit / 64-bit mismatch in its return value. This error could occur when logging was enabled, for example when using configuration settings such as:[Driver] option=524292
(Bug #16367440, Bug #68201)
Trailing zeros for the fractional part of the second for
datetime
andtimestamp
values were not removed for MySQL server version 5.5 or earlier, which do not support fractional second. (Bug #16294197, Bug #65418)Microsoft Access could experience a severe error when updating a
BIT
column in view representing a MySQL table, for example through the datasheet interface. (Bug #16287859, Bug #68243)When binding text data to a numeric or decimal field with
SQLBindParameter
, Connector/ODBC always used the system locale to determine the thousands and decimal separators. This resulted in errors when, for example, a decimal separator in a number expressed in the British or American notation (“.”) is treated as a thousands separator and removed during the binding because Connector/ODBC was running on a non-English OS. To avoid the error, this fix makes Connector/ODBC use the comma (“,”) as the thousands separator and the period (“.”) as the decimal separator for binding if theFLAG_NO_LOCALE
connection option is set; if the option is not set, Connector/ODBC continues to follow the system locale in interpreting and binding the numbers. (Bug #11766369, Bug #59469)