Documentation Home
MySQL Connector/ODBC Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 403.1Kb
PDF (A4) - 402.5Kb

MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 8.x  /  Changes in MySQL Connector/ODBC 8.0.29 (2022-04-26, General Availability)

Changes in MySQL Connector/ODBC 8.0.29 (2022-04-26, General Availability)

Security Notes

Functionality Added or Changed

  • Added the following TLS/SSL option aliases to align with other MySQL connectors: ssl-mode (SSLMODE), ssl-ca (SSLCA), ssl-capath (SSLCAPATH), ssl-cert (SSLCERT), ssl-cipher (SSLCIPHER), and ssl-key (SSLKEY). The ODBC driver, GUI, and myodbc-installer use these new aliases by default instead of the old option names. For example, setting SSL Key in the GUI now saves it as ssl-key instead of SSLKEY. (WL #14845)

  • Added FIDO Pluggable Authentication support, an authentication mechanism added in MySQL Enterprise Edition 8.0.27. For additional details, see Authentication Options. (WL #14877)

Bugs Fixed

  • Extended SQLGetTypeInfo() to return results for Unicode wide character type IDs, such as SQL_WCHAR, when before only their corresponding ANSI character type IDs such as SQL_CHAR returned results. (Bug #33772516)

  • On Windows, installing the driver to a custom location made setting PLUGIN_DIR required to find bundled plugins. Now the directory location is used to determine the plugin directory unless PLUGIN_DIR is specified. (Bug #33720924)

  • The ODBC driver would unexpectedly halt when connecting to accounts that required client-side authentication plugins if those plugins depended on 3rd-party libraries (such as authentication_fido and libfido2.dll) that could not be found or loaded. Now it reports an error instead. (Bug #33702043)

  • The SQLColumns() function result included the length qualifier for some types, such as char(16) instead of char. (Bug #33599093)

  • With prepared statements and NO_CACHE=1, having a NULL value in a row column would nullify a value in the same column of the next row. This produced an incorrect value giving NULL where a non-value was expected. (Bug #106683, Bug #33951069)

  • When a Catalog or Schema is not specified, and if a table with the same name and set of columns existed in another database, SQLColumns() would return data from multiple databases instead of only the current database. In this case, MS Access would yield an error as the database name was not checked for. Now only data from the current database is returned, unless specifically specified. (Bug #106204, Bug #33788407)

  • On Windows, the ODBC GUI dialog did not display all available inputs; so the dialog window size was increased accordingly. (Bug #106013, Bug #33624658)