adbcBridge notes

adbcBridge notesWhat the drivers did, written down.https://adbcbridge.org/notes/2026-09-04T00:00:00Zthe adbcBridge maintainerAltibase ODBC stores astral characters as CESU-8 on its wide pathhttps://adbcbridge.org/notes/altibase-odbc-findings/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

Altibase ODBC 7.3 disagrees with itself above the BMP, reports CREATE_PARAMS "precision" so a generated VARCHAR is VARCHAR(1) (22026), and numbers its byte types outside ODBC.

Three things Exasol's ODBC driver gets wrong about C types and block cursorshttps://adbcbridge.org/notes/exasol-odbc-three-quirks/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

Exasol ODBC 25.2/26.2 refuses SQL_C_BINARY outright (HY003), fails a NULL SQL_DECIMAL parameter bound SQL_C_DEFAULT (SI002), and claims SQL_GD_BLOCK it cannot deliver.

A 35-character Driver=, a compiled-in path, and a CLOB at eight rows a secondhttps://adbcbridge.org/notes/ibm-i-access-odbc-on-linux-and-macos/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

IBM i Access ODBC 1.1.0.29 against Db2 for i 7.5 — the Driver= value must stay under 36 characters, the libraries need a real /opt/ibm/iaccess, and a CLOB column costs a round trip per row.

The Ingres ODBC client kills any Java process that loads ithttps://adbcbridge.org/notes/ingres-client-and-the-jvm/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

Three defects in the Actian Ingres 10.1 ODBC client, each with its exact error text - the signal-handler takeover that aborts a JVM, the four-byte SQLWCHAR that truncates the connection string under unixODBC, and the 32-byte Driver= buffer.

Kinetica's ODBC driver executes parameter N with the value bound at N+1https://adbcbridge.org/notes/kinetica-odbc-parameters-off-by-one/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

Kinetica ODBC 7.1.9 accepts every SQLBindParameter and then shifts the values one position, sending the last as NULL under SQL_SUCCESS with an empty diagnostic queue.

Which older engine releases pass the matrix entry unchangedhttps://adbcbridge.org/notes/older-releases-that-still-pass/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

A sweep of older SQL Server, PostgreSQL, MariaDB and Firebird releases through the same driver and the same unmodified matrix entry, with only the port changed.

The SAP HANA ODBC client decodes narrow statement text as Latin-1https://adbcbridge.org/notes/sap-hana-odbc-latin-1-and-type-table/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

SAP HANA client ODBC 2.29.25 (libodbcHDB) takes narrow SQL and SQL_C_CHAR parameters as Latin-1, not UTF-8, and returns its type table alphabetically so SECONDDATE outranks TIMESTAMP.

SingleStore's ODBC connector loses SQLGetTypeInfo under ANSI_QUOTEShttps://adbcbridge.org/notes/singlestore-odbc-connector-findings/2026-09-04T00:00:00Z2026-09-03T00:00:00Z

Two defects in SingleStore Connector/ODBC 1.2.2 with their exact errors - SQLGetTypeInfo failing 42S22 under ANSI_QUOTES, and a SQLColumns segfault on a NULL catalog - and what it gets right.

A parameter array in Ignite's ODBC driver takes every row's NULL flag from row 0https://adbcbridge.org/notes/apache-ignite-odbc-findings/2026-09-04T00:00:00Z2026-08-29T00:00:00Z

Apache Ignite's ODBC driver drops a NULL below the first row of a column-wise parameter array - a character column stores an empty string, a BINARY column segfaults the client inside SQLExecute.

A bound NULL becomes an empty string, and a parameter array stops at set 1https://adbcbridge.org/notes/clickhouse-odbc-findings/2026-09-04T00:00:00Z2026-08-29T00:00:00Z

What clickhouse-odbc 1.5.5 does when you write through it - SQL_NULL_DATA ignored when a value buffer is bound, parameter arrays that land two rows of five, and no affected-row count.

Five things OpenLink Virtuoso's ODBC driver does silently and wronglyhttps://adbcbridge.org/notes/virtuoso-odbc-five-defects/2026-09-04T00:00:00Z2026-08-29T00:00:00Z

virtodbc.so from libvirtodbc0 7.2.12 stores UTF-16 text as garbage, aborts on any Charset= but the literal UTF-8, stores every SQL_C_SBIGINT as 0, and strides date parameter arrays by ColumnSize.

Three ways Firebird's ODBC driver loses your parameters without saying sohttps://adbcbridge.org/notes/firebird-odbc-parameter-defects/2026-09-04T00:00:00Z2026-08-28T00:00:00Z

Firebird ODBC 3.0.1 and 3.5.0-rc1 stride fixed-type parameter arrays by BufferLength, write NULL for every SQL_C_SBIGINT after a character bind, and discard ROWS_FETCHED_PTR set before SQLPrepare.

What the Arrow Flight SQL ODBC driver claims, and what it doeshttps://adbcbridge.org/notes/arrow-flight-sql-odbc-findings/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

Arrow Flight SQL ODBC 0.9.7, the driver Dremio publishes, advertises SQLBindParameter while answering HYC00, segfaults in SQLColumns without field metadata, and is iODBC-width on Apple Silicon.

Two ways a Go ODBC program dies before it prints anythinghttps://adbcbridge.org/notes/go-odbc-and-arrow-finalizers/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

alexbrainman/odbc takes an access violation inside api.SQLGetDiagRec on Windows; on Linux and macOS an arrow-go finalizer releases an ArrowArrayStream mid-cgo and takes the process down.

Vendor macOS drivers are built for iODBC's four-byte SQLWCHARhttps://adbcbridge.org/notes/macos-iodbc-width-vendor-drivers/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

MySQL Connector/ODBC 26.7.1, Virtuoso 7.2.17 and Arrow Flight SQL ODBC 0.9.7 for macOS ship as iODBC-width drivers, and under unixODBC they return empty diagnostics or abort the process.

Any text read as a timestamp comes back as today's date, under SQL_SUCCESShttps://adbcbridge.org/notes/opensearch-sql-odbc-findings/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

OpenSearch SQL ODBC 1.5.0.0 converts any character value to today's date when asked for SQL_C_TYPE_TIMESTAMP, and its SQLError never returns SQL_NO_DATA, so a failed connect hangs unixODBC forever.

Where PostgreSQL-wire servers part company with PostgreSQLhttps://adbcbridge.org/notes/postgresql-wire-servers-and-psqlodbc/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

Seven ways CrateDB, QuestDB, Materialize, RisingWave, ArcadeDB, Spanner and YDB answer psqlodbc 16 differently from PostgreSQL 16, each with the error text it produces.

Two psqlodbc bugs that lost rows and narrowed integers, and two trapshttps://adbcbridge.org/notes/psqlodbc-two-fixes-and-two-traps/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

psqlodbc silently discarded a committed transaction on servers without SAVEPOINT and narrowed an out-of-range int8 to -1; both are fixed, and two version-and-build traps remain.

SQL_ERROR with no diagnostic, and a status array nobody writeshttps://adbcbridge.org/notes/sqliteodbc-numeric-and-param-status/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

sqliteodbc 0.99991 fails SQLGetData(SQL_C_NUMERIC) with a bare SQL_ERROR and zero diagnostic records, and accepts SQL_ATTR_PARAM_STATUS_PTR without ever writing to it.

Four conversions taos-odbc calls "not implemented yet", and one that abortshttps://adbcbridge.org/notes/tdengine-taos-odbc-findings/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

taos-odbc at 3.3.6.13 has no TIMESTAMP_STRUCT conversion, one route into a BOOL parameter and no DECIMAL at all, and it aborts the whole process when a client asks for ODBC 3.80.

A NULL column that reads back as the previous row's valuehttps://adbcbridge.org/notes/thirty-two-bit-sqllen-on-64-bit-linux/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

IBM's Db2 clidriver (Db2 and Informix) and Actian Ingres' driver are built with a four-byte SQLLEN on 64-bit Linux, so indicators are read at the wrong stride and NULLs disappear.

The process dies with SIGABRT on the first SQL error, and it is the managerhttps://adbcbridge.org/notes/unixodbc-four-byte-sqlwchar/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

unixODBC 2.3.12 and 2.3.14 overwrite their own stack reading the first SQL_ERROR diagnostic from a driver whose SQLWCHAR is four bytes - Virtuoso and Arrow Flight SQL on macOS, Ingres on Linux.

Five Windows-only ODBC failures are one thing wearing different clotheshttps://adbcbridge.org/notes/windows-ansi-code-page-three-disguises/2026-09-04T00:00:00Z2026-08-25T00:00:00Z

Five drivers that pass on Linux fail on Windows on text: the system ANSI code page sits between the caller and the driver, and the repairs differ only in which call has to leave the wide path.

MariaDB Connector/ODBC 3.2 segfaults on a NULL DATE in a parameter arrayhttps://adbcbridge.org/notes/mariadb-connector-odbc-findings/2026-09-04T00:00:00Z2026-08-24T00:00:00Z

Five findings in MariaDB Connector/ODBC with their exact errors - 3.2's array segfault and wrong row counts, its connect-time DUAL probe, its binary-literal path, and 3.1.15's missing NUL terminator.

What MySQL Connector/ODBC does to a DATETIME(6), and six other findingshttps://adbcbridge.org/notes/mysql-connector-odbc-findings/2026-09-04T00:00:00Z2026-08-24T00:00:00Z

Seven findings in MySQL Connector/ODBC 9.4, 8.4 and 26.7.1 with their exact errors - the fractional seconds pyodbc loses, a SIGFPE in get_column_size, two segfaults, and four platform traps.

A Unicode string parameter cannot reach a MySQL-wire warehouse's preparehttps://adbcbridge.org/notes/mysql-wire-warehouses-prepared-statements/2026-09-04T00:00:00Z2026-08-24T00:00:00Z

Six servers behind MySQL Connector/ODBC 9.4 - what their server-side prepare does with a BLOB-typed string, a MYSQL_TYPE_NULL, a BIT array of NULLs, and a connector probe that assumes DUAL.

Oracle's SQORA driver takes a rowset change, then crashes or loses rowshttps://adbcbridge.org/notes/oracle-instant-client-odbc-findings/2026-09-04T00:00:00Z2026-08-24T00:00:00Z

Oracle Instant Client ODBC 23 (SQORA) accepts SQL_ATTR_ROW_ARRAY_SIZE on an open cursor and then segfaults in bcoReturnColData or silently drops rows; CLOB columns read a row at a time.

Four things DuckDB's ODBC driver does that a caller has to know abouthttps://adbcbridge.org/notes/duckdb-odbc-findings/2026-09-04T00:00:00Z2026-08-23T00:00:00Z

DuckDB ODBC 1.5.5 - SQLGetInfo(SQL_DBMS_VER) segfaults, a parameter array stores set 0 in every row, a C++ exception across the FFI aborts Rust, and :memory: is a new database per connection.

SQLColumns segfaults on a NULL NUMERIC_PRECISION from mongosqldhttps://adbcbridge.org/notes/mongodb-bi-connector-through-mysql-odbc/2026-09-04T00:00:00Z2026-08-23T00:00:00Z

MySQL Connector/ODBC 9.4 runs strtol() on the NULL NUMERIC_PRECISION the MongoDB BI Connector reports for a DECIMAL column, and the process dies inside SQLColumns.