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


MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 9  /  Changes in MySQL Connector/ODBC 9.2.0 (2025-01-21, General Availability)

Changes in MySQL Connector/ODBC 9.2.0 (2025-01-21, General Availability)

Functionality Added or Changed

  • Added a new WEBAUTHN_DEVICE_NUMBER connection option that is passed to and interpreted by the WebAuthN authentication plugin. It accepts a numeric value that selects the authenticator device to use during WebAuthN authentication. Previously, the first (#0) authentication plugin was always used. (WL #16646)

Bugs Fixed

  • The user defined traceparent query attribute in an OpenTelemetry instrumented application was not sent to the server, which resulted in user (or connector) generated OpenTelemetry spans to not associate with the corresponding server spans. (Bug #37188732)

    References: This issue is a regression of: Bug #36841317.

  • Retrieving a list of records that contained an empty BLOB field could return an unexpected result. (Bug #116657, Bug #37286526)

  • For fixed column types, such as CHAR, having these fields contain unexpected multi-byte characters could cause a "returned data that does not match expected data length for column" error.

    The connector now enables the PAD_CHAR_TO_FULL_LENGTH sql_mode. (Bug #114470, Bug #37298936)

  • Improved result set handling produced by catalog functions. When SQLFreeStmt() with SQL_UNBIND or SQL_RESET_PARAMS was called after a catalog function (such as SQLProcedureColumns), the result set produced by the catalog function was not cleared in accordance to ODBC API requirements for unbinding result columns and resetting parameters. (Bug #109466, Bug #36906892)