docs: plain-ODBC re-verification of seven more entries (DuckDB, OceanBase, RisingWave, GreptimeDB, Materialize, YDB, ArcadeDB) - #8
Merged
Conversation
Every driver and server claim in the DuckDB, OceanBase, RisingWave, GreptimeDB, Materialize, YDB and ArcadeDB entries was re-run with standalone ODBC C programs (no adbcBridge in the stack) and adversarially re-checked before wording changed. DuckDB, GreptimeDB, YDB, Materialize: every claim holds; no entry text changes. RisingWave: the entry does rely on psqlodbc's UseServerSidePrepare=0 -- the server keeps a statement name after the client closes it, so the usual allocate/prepare/ execute/free loop fails on its second query (parameters or not); FLOAT(p) is the one type modifier the parser takes; a write reaches a scan at the next barrier, FLUSH forces one at once rather than waiting. ArcadeDB: SQLTables(SQL_ALL_TABLE_TYPES) answers SQL_ERROR; only SQLColumns answers success with zero rows. OceanBase: the ~10x MySQL comparison and the "fastest MySQL-wire entry" claim do not reproduce and are removed; 105k rows/s is stated at its row count; array binding changes nothing there; obd's open-files check fires only on the MINI path; the NULL rule was inverted -- the NULL-carrying execute of a fresh prepared statement is the one refused (4001), later NULLs go through -- and on bulk ingest the fallback drops leading NULL-bearing rows silently, which is now recorded. Materialize (tests/compat/README.md): psqlodbc batches 100 inlined statements per round trip; the split is not a text-width limit. UPSTREAM.md: five new documented-not-yet-reported rows (DuckDB ODBC Linux, RisingWave, OceanBase, ArcadeDB, psqlodbc silent commit-after-rollback). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018p4RMAn1YewPrhWtLT5ogj
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018p4RMAn1YewPrhWtLT5ogj
singhpratech
added a commit
that referenced
this pull request
Aug 29, 2026
…g page Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018p4RMAn1YewPrhWtLT5ogj
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every driver and server claim in seven more COMPATIBILITY.md entries was re-run with standalone ODBC C programs (no adbcBridge in the stack) and independently re-checked before any wording changed.
No text changes needed: DuckDB, GreptimeDB, YDB, Materialize — every claim held.
RisingWave: the entry relies on psqlodbc's
UseServerSidePrepare=0(the server keeps a statement name after the client closes it, so the usual allocate/prepare/execute/free loop fails on its second query, parameters or not);FLOAT(p)is the one type modifier the parser takes; a write reaches a scan at the next barrier, andFLUSHforces one at once rather than waiting.ArcadeDB:
SQLTables(SQL_ALL_TABLE_TYPES)answersSQL_ERROR; onlySQLColumnsanswers success with zero rows.OceanBase: the "~10x MySQL" comparison and the "fastest MySQL-wire entry" claim do not reproduce and are removed; 105k rows/s is stated at its row count; array binding changes nothing there;
obd's open-files check fires only on the MINI path; the NULL rule was inverted — the NULL-carrying execute of a fresh prepared statement is the one refused (4001), later NULLs go through — and on bulk ingest the fallback drops leading NULL-bearing rows silently, which is now recorded.Materialize (
tests/compat/README.md): psqlodbc batches 100 inlined statements per round trip; the split is not a text-width limit.UPSTREAM.md: five new documented-not-yet-reported rows (DuckDB ODBC on Linux, RisingWave, OceanBase, ArcadeDB, psqlodbc silent commit after a server-side rollback).