# Connector/ODBC 3.1.19 Release Notes

The most recent [***Stable***](https://mariadb.com/docs/release-notes/community-server/about/release-criteria) ***(GA)*** release of MariaDB Connector/ODBC is:[**MariaDB Connector/ODBC 3.2.5**](https://mariadb.com/docs/release-notes/connectors/odbc/3.2/3.2.5)

[Download](https://mariadb.com/downloads/#connectors)[Release Notes](https://mariadb.com/docs/release-notes/connectors/odbc/3.1/3.1.19)[Changelog](https://mariadb.com/docs/release-notes/connectors/odbc/changelogs/3.1/3.1.19)[About MariaDB Connector/ODBC](https://github.com/mariadb-corporation/docs-release-notes/blob/test/kb/en/about-mariadb-connector-odbc/README.md)

**Release date:** 7 Jul 2023

This is a [Stable (GA)](https://mariadb.com/docs/release-notes/community-server/about/release-criteria) release of MariaDB Connector/ODBC 3.1.

MariaDB Connector/ODBC 3.1.19 is built on top of [MariaDB Connector/C v.3.3.5](https://mariadb.com/docs/release-notes/connectors/c/3.3/3.3.2).

## Bug Fixes

* [ODBC-350](https://jira.mariadb.org/browse/ODBC-350) - Invalid BIT column value from subselect
* [ODBC-390](https://jira.mariadb.org/browse/ODBC-390) - Using SQL\_ATTR\_QUERY\_TIMEOUT leaks memory
* [ODBC-391](https://jira.mariadb.org/browse/ODBC-391) - With lower\_case\_table\_names=2 server the driver may not read indexes in SQLStatistics. This issue caused [ODBC-370](https://jira.mariadb.org/browse/ODBC-370) - MS Access could not detect table's indexes
* [ODBC-392](https://jira.mariadb.org/browse/ODBC-392) - SQLSetConnectAttr(SQL\_ATTR\_CURRENT\_CATALOG) can work incorrectly

## Changelog

For a complete list of every change made in this release, with links to\
detailed information on each push, see the [changelog](https://mariadb.com/docs/release-notes/connectors/odbc/changelogs/3.1/3.1.19).

<sub>*This page is: Copyright © 2025 MariaDB. All rights reserved.*</sub>

{% @marketo/form formid="4316" formId="4316" %}