The Ultimate Guide to High Availability with MariaDB

MariaDB Connector/ODBC 3.1.19 Changelog

You are viewing an old version of this article. View the current version here.

The most recent Stable (GA) release of MariaDB Connector/ODBC is:
MariaDB Connector/ODBC 3.2.3

Download Release Notes Changelog About MariaDB Connector/ODBC

Release date: 7 Jul 2023

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on GitHub. On GitHub you can view more details of the revision and view diffs of the code modified in that revision.

  • Revision #08da03f 2023-06-10 21:58:33 +0200
    • Overriding the problem with c/c requires C99 with older GCC
  • Revision #fc52d66 2023-06-10 12:42:29 +0200
  • Revision #a210bfa 2023-06-05 12:44:14 +0200
    • ODBC-391 Only the fix as lower_case_table_names can't be changed for session. i.e. the test has been added, but to server has to be in lower_case_table_names=2 mode to test the fix, otherwise it ensures that the fix doesn't break catalog functions against server in "normaler" mode. The fix adds reading of the lower_case_table_names, and if it's 2, then it compares table name case insensitively where case sensitive comparison would be used otherwise. The problem actually affects not ony SQLStatistics, but almost all catalog functions, that take catalog and/or table parameter as ordinary argument.
  • Revision #60a5bd6 2023-06-02 14:03:09 +0200
  • Revision #9b96270 2023-05-17 10:28:42 +0200
    • Fix of potential issue found with ASAN
  • Revision #2eb9877 2023-05-15 10:16:55 +0200
    • Added WITH_ASAN, WITH_UBSAN and WITH_MSAN cmake option to enable
  • Revision #c0d989b 2023-04-28 12:34:59 +0200
    • ODBC-390 Using SQL_ATTR_QUERY_TIMEOUT leaks memory
  • Revision #313102f 2023-04-13 13:47:37 -0400
    • bump the VERSION

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.