MariaDB is pleased to announce the immediate availability of the MariaDB Connector/ODBC 3.1.16 GA release.
MariaDB Connector/ODBC 3.1.16
MariaDB Connector/ODBC 3.1.16 is a Stable (GA) release. Notable changes in this release include:
- MariaDB Connector/ODBC is now based on MariaDB Connector/C 3.3 release series. This release, 3.1.16, is based on MariaDB Connector/C 3.3.1
- A failover feature has been added.
- MariaDB Connector/ODBC 3.1.16 is statically linked for Windows and macOS with MariaDB Connector/C 3.3.1
- MariaDB Connector/ODBC 3.1.16 is dynamically linked for Linux with MariaDB Connector/C. MariaDB Connector/C versions 3.2 or greater can be used, but version 3.3 or greater is required for the failover feature.
- The NULLISCURRENT connection string option has been added. NULLISCURRENT allows forcing a NULL catalog name value to be treated as the currently selected schema in SQLTables(). If NULLISCURRENT is not used, a NULL catalog name value is treated as “any” schema and SQLTables() returns tables from all databases.
- The NOLOCALINFILE connection string option has been added. A non-zero value for NOLOCALINFILE disables LOAD DATA LOCAL INFILE execution. A zero value enables it. By default LOAD DATA LOCAL INFILE is enabled.
- Release tarball layout has been cleaned up and re-organized.
Issues fixed in this release include:
- If the NULL SQL_C_WCHAR buffer is bound in SQLBindCol to obtain the required buffer length, a segmentation fault can occur.
- MariaDB Connector/ODBC package for macOS is missing the Connector/C runtime library.
- Fixed use of indexes in search for the best row identifier for positioned operations.
- Connecting to some server versions that do not support session tracking causes an Unknown system variable ‘session_track_schema’ error. In particular, this bug occurs if connecting to MariaDB Xpand.
- If a UNIQUE index on a nullable column is used, MS Access could pick up that index for use and get wrong data.