Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Release Notes for MariaDB Connector/ODBC 3.2
Release date: 30 May 2025
This is a Stable (GA) release of MariaDB Connector/ODBC 3.2.
MariaDB Connector/ODBC 3.2.6 is built on top of MariaDB Connector/C v.3.4.5.
- Crash in SQLExecDirect on UPDATE statement with array of parameters
- The destructor releasing server side prepared statement could throw and this exception would not be caught
- MS Access won't work with the linked table if best row id is BIGINT
- MS Access shows record with AUTO_INCREMENT primary key as #Deleted after insert that does not specify that field value
- SQLExecDirect on array of parameters could issue multistatement query even if multistatement option had not been selected for the connection.
- Multiple issues with current implementation of SQLCancel
- SQLCancel could run on already dropped statement due to race condition
- Possible crash in SQLCancelHandle
- Introduced option TRUNCDT to skip time truncation error. Setting it to non-zero value makes connector not to return error on date/time type parameter value truncation. These are when value for SQL_TIME contains fractional part, or for SQL_DATE contains non-zero time. In particular, that permits to insert value with fractional part into TIME field which in MariaDB can have fractional part as ODBC SQL_TIME type
For a complete list of every change made in this release, with links to detailed information on each push, see the .
Release date: 10 Oct 2025
This is a Stable (GA) release of MariaDB Connector/ODBC 3.2.
MariaDB Connector/ODBC 3.2.7 is built on top of MariaDB Connector/C v.3.4.7.
- SSLVERIFY=0, still getting The certificate's CN name does not match the passed value on Windows
- Dropping statement handle could break protocol if other statement hasn't finished fetching results
- Fetching of stored procedure out parameters could fail in case of result-set streaming
- Some internal classes destructors called functions that can throw in some conditions
- SQLGetData could write data of the wrong length in case of resultset streaming and cached resultset
- Bulk operations with parameter callbacks could not respect NULL value indicators
- The connector did not support SQL_POSITIONED_STATEMENTS information type
For a complete list of every change made in this release, with links to detailed information on each push, see the .
Download | Release Notes | Changelog | About MariaDB Connector/ODBC
Release date: 14 Nov 2024
This is a Stable (GA) release of MariaDB Connector/ODBC 3.2.
MariaDB Connector/ODBC 3.2.4 is built on top of .
- High Prepared_stmt_count after freeing statement handles
- "Verify certificate" checkbox in TLS options of the setup dialog gets checked by default. This may result in it being saved and used unintentionally for connections.
- Latest ODBC driver returns NULL characters in strings with characters requiring >1 byte in utf8 representation
- Incorrect value for charset utf8mb4 and longtext column with multibyte unicode characters
For a complete list of every change made in this release, with links to detailed information on each push, see the .
Release date: 19 Dec 2025
This is a Stable (GA) release of MariaDB Connector/ODBC 3.2.
MariaDB Connector/ODBC 3.2.8 is built on top of MariaDB Connector/C v.3.4.8.
- SQLSetPos can delete unintended row(s) if the available index is unique and part of the key for the deleted record is NULL
- Crash at the attempt to read out of range column number
- Incorrect work of SQLDescribeCol with NULL name buffer
- ADODB crashes on the call to SQLCancel
- Problem with SQLSetPos on block cursor with NULL values
For a complete list of every change made in this release, with links to detailed information on each push, see the .
ODBC-444 - Errors "[42000] [ma-3.2.3]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE @@sql_mode LIKE '%ansi_quotes%'" while running queries with MariaDB ODBC 3.2.3 and MySql 5.7
ODBC-440 - MSI doesn't update DSNs referring 3.1 driver
ODBC-441 - Setup dialog is missing fields for prepared statements cache control. Added fields for the cache size and the maximal length of cached statement.
ODBC-66 - Support ODBC 3.8 standard The driver is now compliant with ODBC standard version 3.8. Mainly that means implementation of SQLCancelHandle API function and SQL_ATTR_RESET_CONNECTION connection attribute support.
ODBC-397 - Add Prepared Statement Cache to the Connector.
The driver now uses cache for server side prepared statements, that allows not to re-prepare statements, but use them from the cache. Application can configure the cache with PSCACHESIZE and MAXCACHEKEY connection string options. The former sets the size of the cache, i.e. the number of statements that will be cached, the latter is the maximal size of the cache key, that effectively limits the maximum query length, that will be the value of MAXCACHEKEY - length of the current schema name - 1.
Connector/ODBC is now available as RPM and DEB packages for selected platforms(RHEL, Ubuntu, Debian)
Improved protocol resilience in case of resultset streaming. In the version 3.1 if the resultset streaming is used, it will block the connection, and the driver will return error on any new query. The 3.2.1 driver in this case will cache the rest of currently streamed resultset, and execute the new query without error
For a complete list of every change made in this release, with links to detailed information on each push, see the changelog.
ODBC-222 - SQLExecDirect ODBC API function now uses text protocol and client side prepared statements(CSPS). That can be automatically switched to use of binary protocol and server side prepared statement(SSPS) if necessary(for example for CALL statement).
ODBC API function SQLPrepare uses by default SSPS, but it can switch to CSPS, for example in case of multistatement query.
The connection string option PREPONCLIENT to use CSPS by default also in SQLPrepare has been added. In some cases driver will still revert to use of SSPS even if this option is selected. One example of such case is a request of resultset metadata before SQLExecute API function call.
ODBC-86 - parameter array operations are now optimized also for the case of text protocol and CSPS use. i.e. driver can construct batch of queries based on values in parameter arrays for sending it via text protocol. Sending parameter arrays via binary protocol is supported already in 3.1 version and is preferable way for this operation.
ODBC-290 - Cursor type now defaults to SQL_CURSOR_FORWARD_ONLY as it is required by specs. 3.1.x series has default cursor type SQL_CURSOR_STATIC
- NULL value of catalog name parameter of SQLTables ODBC API function is now treated as "current schema" by default, and not as "any schema"
- Support of connection attributes. For setting connection attributes the ATTR connection string option can be used in following format
For a complete list of every change made in this release, with links to detailed information on each push, see the changelog.
ODBC-424 - Can't open connection from .NET application to MySQL 8.4
ODBC-426 - SQLForeignKeys call may result in error with MySQL server
ODBC-427 - Out parameters won't be written to parameter buffers with MySQL server
ODBC-429 - AccessViolationException when executing a SELECT on a non existing table
ODBC-430 - Wrong reported max size for VARCHAR and VARBINARY
ODBC-431 - Result-set streaming doesn't work with binary results
ODBC-432 - Driver fails to cache multiple results
ODBC-433 - SQLMoreResults may pick other statement's results
ODBC-435 - SQLPrimaryKeys call returns incorrect KEY_SEQ field
For a complete list of every change made in this release, with links to detailed information on each push, see the changelog.
Download | Release Notes | Changelog |
Release date: 24 Feb 2025
This is a Stable (GA) release of MariaDB Connector/ODBC 3.2.
MariaDB Connector/ODBC 3.2.5 is built on top of MariaDB Connector/C v.3.4.4.
MariaDB ODBC drivers of 3.2 series can use both text and binary protocol, i.e. prepare statements on the client or on the server side, with text protocol being the default for direct execution(SQLExecDirect() function) and binary protocol for prepared statements(SQLPrepare()+SQLExecute() functions). This release provides applications more control on what protocol to be used
- Introduced connection string option EDSERVER to force SQLExecDirect to use server side prepared statements(SSPS)/binary protocol. This option compliments introduced earlier PREPONCLIENT option making SQLPrepare+SQLExecute to prepare query on the client side
- Added statement and connection attributes to control where queries are prepared by SQLExecDirect and SQLPrepare. These attributes are MariaDB specific, i.e. they will be ignored by other ODBC drivers. The attribute type values are SQL_ATTR_EXECDIRECT_ON_SERVER=25100 and SQL_ATTR_PREPARE_ON_CLIENT=25101
- Wrong naming pattern for deb packages assembled by cpack
- When trying to use ODBC command FillSchema I get a crash every time / module faulting
- Milliseconds are truncated
- GPF on modifying VarChar-Field with more than 4001 Bytes after calling any Stored Procedure
For a complete list of every change made in this release, with links to detailed information on each push, see the .
ATTR={<attrname1>=<attrvalue1>[,<attrname2=attrvalue2,...]}ODBC-454 - SQLForeignKeys reports error
ODBC-421 - The driver has been moved to use Connector/C 3.4 series driver. The most important change implied by that, is that certificate verification option (SSLVERIFY) is now by default on if encrypted connection is requested by the application.
ODBC-163 - Support of new C/C callback system for custom data type conversion. There are 2 types of callbacks - for parameters and result.
Parameter callbacks are used for bulk operations and allow to minimize memory use required for data type conversions. Their use controlled by the connection string option PCALLBACK, which is on by default.
Result callbacks are designed to make certain types of conversions faster and also reduce memory use, as they can write directly to application buffers and do not allocate intermediate buffers normally required for conversion. The option to turn on result callbacks is RCALLBACK and it is off by default.
ODBC-410 - SQLForeignKeys performance optimization. The function could be noticeably slow in the case of a large number of schemas in the database. The optimization makes it significantly faster in such cases.
ODBC-418 - Widechar string data gets truncated if it contains a NULL character
For a complete list of every change made in this release, with links to detailed information on each push, see the changelog.
Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.