docs: ArcadeDB #8090 fixed in #8096, verified on the 26.10.1 snapshot - #141
Merged
Merged
Conversation
Luca Garulli merged the fix at 04:07 UTC on 2026-09-22, closing the issue with "Fixed in 26.10.1". Retested here the same day on the 26.10.1-SNAPSHOT image (build 382ae09d, sixty commits past the merge commit): the space-and-fraction literal and the bound timestamp parameter both round-trip to the microsecond, an unreadable value now fails the write with SQLSTATE 22023 instead of storing NULL, and the column reaches Arrow as timestamp[us] rather than a string. A second machine ran psycopg over libpq 18 in both parameter formats plus psqlodbc 18 and agreed on every case. The compatibility notes now scope the T-literal requirement to the released 26.9.1 and record one shape still refused after a space separator, a trailing offset given to the second. The tracker row says "fixed" and waits on the 26.10.1 release for the shipped-in line.
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.
ArcadeDB merged the fix for the timestamp that stored
NULLunder a successfulINSERTat 04:07 UTC today, closing #8090 with "Fixed in 26.10.1". This records it and the retest.Verified, not assumed. The
26.10.1-SNAPSHOTimage pushed at 14:20 UTC reports build382ae09d, which GitHub compare puts 60 commits ahead of and 0 behind the merge commit57e48d7a03, so the fix is in the image. Tested on the same machine and harness that produced the 26.9.1 baseline, psqlodbc 16 then adbcBridge 0.1.3 into Arrow:'2024-02-29T13:45:10.123456''2024-02-29 13:45:10.123456''2024-02-29 13:45:10'SQL_TYPE_TIMESTAMPparameter'not-a-timestamp'The column also now arrives as Arrow
timestamp[us]; on 26.9.1 the same column came back as a string. A second machine ran an independent route the same day — psycopg over libpq 18.0.6 in both the text and the binary parameter format, plus psqlodbc 18.00.0004 — and agreed on every shared case.One shape is still refused after a space separator, a trailing offset given to the second (
+05:30:00); it is accepted after aT, and+05,+05:30andZare accepted after either. That is recorded in the compatibility notes as the smaller thing it is — it refuses rather than losing anything silently.Changes:
docs/UPSTREAM.md— the row moves to fixed, with the PR link, what changed, and what the retest showed. The status widget already renders an issue closed as completed as fixed, so no script change is needed.tests/compat/README.md— theT-literal bullet is now scoped to the released 26.9.1, carries the retest, and notes the offset shape.docs/COMPATIBILITY.md— the ArcadeDB row says theTrequirement is a 26.9.1 trait.The "fixed in 26.10.1" line waits for that release to ship. Nothing has been posted on the issue.