docs: tracker — fix PRs sent for OpenSearch #101/#102 and ClickHouse's parameter-array half - #150
Merged
Merged
Conversation
…s parameter-array half opensearch-project/sql-odbc#104 (ConnectError never clears its error, so a failed connect spins forever) and #105 (a character value asked for as a datetime came back as today's date) were opened 2026-09-24. ClickHouse/ clickhouse-odbc#588 covers the second half of #582; the maintainer's review asked for the ODBC error-path contract, which was added the same day and verified on a driver built from the branch. None of the three has landed. The rows say what each PR does and how far it was verified, which for the OpenSearch pair is a syntax check only.
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.
Three tracker rows catch up with pull requests sent this week. None has landed; each row now names its PR, what it changes, and how far it was verified — which differs a lot between them, and the rows say so.
OPENSEARCHAPI_ConnectErrornever cleared the connection error after reporting it, so unixODBC'sSQLDriverConnect(W)loop overSQLErrorWnever reachedSQL_NO_DATA_FOUNDand a failed connect spun at 100% CPU. Four lines, following the patternEN_get_error()already uses for the environment.SQL_SUCCESS; character sources now go throughtimestamp2stime()and an unreadable string returns 22018 — which required adding that SQLSTATE, sinceSTMT_STRING_CONVERSION_ERRORhad none.Verification is stated honestly per row. The OpenSearch pair is syntax-checked only — that repo's CMake hardcodes a 2019 kernel-headers path and its tests need vcpkg, the AWS SDK and a live cluster — so their CI is the first real run. The ClickHouse fix was built and run against a live 26.7.5.10 with the project's own suite, 391 of 392 passing, the one failure being environmental and identical on the released driver.
docs/compatibility.jsonregenerated as CI requires (no content change — these rows are in UPSTREAM.md, not the compatibility table).