> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/release-notes/connectors/odbc/2.0/2.0.16.md).

# Connector/ODBC 2.0.16 Release Notes

Release notes for MariaDB Connector/ODBC 2.0.16, a Stable (GA) release published 8 February 2018.

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

[Download](https://downloads.mariadb.org/connector-odbc/2.0.16)[Release Notes](/docs/release-notes/connectors/odbc/2.0/2.0.16.md)[Changelog](/docs/release-notes/connectors/odbc/changelogs/2.0/2.0.16.md)[About MariaDB Connector/ODBC](/docs/connectors/mariadb-connector-odbc.md)

**Release date:** 8 Feb 2018

This is a [***Stable***](/docs/release-notes/community-server/about/release-criteria.md) ***(GA)*** release of MariaDB\
Connector/ODBC.

MariaDB Connector/ODBC 2.0.16 is built on top of [MariaDB Connector/C v.2.3.5](/docs/release-notes/connectors/c/2.3/2.3.5.md) and uses the binary prepared statement protocol.

## Bug Fixes

* [ODBC-134](https://jira.mariadb.org/browse/ODBC-134): Fetch would fail if an unbound column contained NULL and if for that column some arbitrary descriptor field was set by the application (but not length/indicator buffer pointers). The bug affected ADO, as that is something it can do with CursorLocation adUseClient in some cases.
* [ODBC-119](https://jira.mariadb.org/browse/ODBC-119): The connector ordered SQLStatistics results using the wrong columns. This could cause MS Access to pick the wrong column as a unique index.
* [ODBC-131](https://jira.mariadb.org/browse/ODBC-131): While linking a table, MS Access threw an error when it received an unexpected length for SQLSMALLINT and SQLINTEGER columns in a SQLColumns resultset.
* [ODBC-126](https://jira.mariadb.org/browse/ODBC-126): Core dump when a procedure returned more than 1 result set
* [ODBC-123](https://jira.mariadb.org/browse/ODBC-123): Crashes reading a MariaDB table with LibreOffice
* [ODBC-120](https://jira.mariadb.org/browse/ODBC-120): Performance issue. Connector did redundant calls of mysql\_stmt\_data\_seek
* [ODBC-115](https://jira.mariadb.org/browse/ODBC-115): Wrong rc and sqlstate for numeric overflow (but not for fractional truncation). Now the connector returns 22003 and SQL\_ERROR.
* [ODBC-110](https://jira.mariadb.org/browse/ODBC-110): Crash in the case of columns unbinding after statement execution and before fetching data.
* [ODBC-105](https://jira.mariadb.org/browse/ODBC-105): SQLColumns returns COLUMN\_DEF enclosed by 2 single quotes

## Changelog

For a complete list of every change made in this release, with links to detailed information on each push, see the [changelog](/docs/release-notes/connectors/odbc/changelogs/2.0/2.0.16.md).

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

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