Changes in MySQL Connector/ODBC 9.3.0 (2025-04-15, General Availability)

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• All instances of the deprecated function mysql_real_escape_string() in the source code have been replaced by an internal implementation of myodbc_escape_string(), which works similarly and can also handle the escaping of wildcard characters ('_' and '%') in LIKE expressions. (Bug #116559, Bug #37250400)

• The following Connector/ODBC Connection Parameters can now be configured on the ODBC administrator GUI:

  • readtimeout

  • writetimeout

  • OPENTELEMETRY

  (WL #16587)

Bugs Fixed

• The MSI installer checked for the wrong version of Visual C++ Redistributable required by Connector/ODBC when installing it on a system. With this fix, it now requires the system to have version 14.40 or higher of the Visual C++ Redistributable 2022. (Bug #37536382)

• Reported errors that occurred while executing multiple statements with a single query were generic and without context. For example, SQLMoreResults might return "unhandled error from mysql_next_result()" instead of the error reported by MySQL Server. (Bug #37423741)

  References: This issue is a regression of: Bug #49466, Bug #11757423.

• On macOS, Connector/ODBC failed to create connections to servers for accounts that required pluggable authentication. It was due to faulty links to the 3rd-party libraries bundled with Connector/Python, which were corrected by this patch. (Bug #37090584)

• An assertion failure occurred unnecessarily when SQLBindCol() attempted to bind data to column 0 without bookmarks being enabled. (Bug #18641803)

• Memory leaks occur with the SQLCancel() function, because it failed to free the MYSQL* handle in the case of a failed connection. (Bug #18534345)

• When using server-side prepared statements, fetching a time column bound to the SQL_C_CHAR type returned an incorrect string if the hour value had 3 digits. (Bug #116087, Bug #37071646)

• If the SQLCloseCursor() method was called when no result set was available, no error was returned. With this patch, the method returned SQL State: 24000 and the error message Invalid cursor state in the situation. (Bug #72311, Bug #26474326)