Skip to content

docs: ArcadeDB retested on 26.9.1 — NULL BOOLEAN fixed upstream (#6674), DATETIME_MICROS literal reported as #8090 - #139

Closed
singhpratech wants to merge 1 commit into
mainfrom
docs/arcadedb-26.9.1-retest
Closed

singhpratech wants to merge 1 commit into
mainfrom
docs/arcadedb-26.9.1-retest

Conversation

@singhpratech

Copy link
Copy Markdown
Owner

Retest of the two ArcadeDB behaviours the tracker listed as "documented, not yet reported", prompted by Arcade Data's review of the case-study draft.

Setup: ArcadeDB 26.9.1 official image (arm64, sha256:02a1a74f…) with PostgresProtocolPlugin, on macOS; checked over libpq (psycopg 3) with text and binary result formats, and through psqlodbc 18.00.0004 with adbcbridge 0.1.3 using the matrix connection string (BoolsAsChar=0).

Behaviour 26.8.1 (observed 2026-08-28) 26.9.1 (2026-09-21) Tracker
NULL BOOLEAN arrives as false yes fixed: NULL on text, binary and psqlodbc paths ArcadeData/arcadedb#6674, reported by an ArcadeDB contributor, fixed 2026-08-24, shipped 26.9.1
DATETIME_MICROS literal with space + fraction stored as NULL yes still reproduces (space alone and fraction alone parse; both together → NULL under a successful INSERT) ArcadeData/arcadedb#8090, opened by the maintainer 2026-09-21, credited to this project, severity critical

Changes

  • docs/UPSTREAM.md: the ArcadeDB "documented, not yet reported" row is removed; two rows added to the reported table (#8090 open; #6674 fixed, listed because this tracker carried the symptom).
  • tests/compat/test_matrix.py: the arcadedb entry drops not_null=("bo",); test_matrix.py arcadedb on 26.9.1: PASS (PostgreSQL (via ODBC) 12.0.0) with the all-NULL row check covering bo again.
  • tests/compat/README.md: the two bullets updated to match.

Nothing in COMPATIBILITY.md changes (the entry was and is PASS (read); the ISO-8601 T literal rule still applies).

🤖 Generated with Claude Code

https://claude.ai/code/session_019J3cZWZtvDRnwNwmyqcNFV

…4), DATETIME_MICROS space+fraction literal reported by the maintainer as #8090

The tracker's "documented, not yet reported" row for ArcadeDB carried two
behaviours observed on 2026-08-28 against arcadedata/arcadedb:latest, which was
26.8.1 that day. Retested on the 26.9.1 image on 2026-09-21, over libpq on both
result formats and through psqlodbc 18 with the bridge:

* A NULL BOOLEAN no longer arrives as false. That was ArcadeData/arcadedb#6674,
  reported by an ArcadeDB contributor and fixed on 2026-08-24, shipped in 26.9.1.
  The matrix entry masked it with not_null=("bo",); the flag is removed and the
  entry still passes, with the all-NULL row check covering the column again.
* The DATETIME_MICROS literal with a space separator and a fraction is still
  stored as NULL under a successful INSERT. The maintainer opened
  ArcadeData/arcadedb#8090 for it on 2026-09-21 with the root cause (a blanket
  catch in Type.convert() that returns null at FINE) and a reproducer, credited
  to this project, labelled critical.

Both move to the reported table; tests/compat/README.md says the same.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019J3cZWZtvDRnwNwmyqcNFV
@singhpratech

Copy link
Copy Markdown
Owner Author

Superseded by #138, which carries the same tracker and README correction from the Linux side. The one extra change here, dropping the arcadedb entry's not_null=("bo",) flag, is verified on macOS (test_matrix.py arcadedb PASS on the 26.9.1 image without it, all-NULL row check covering bo) and can follow once the matrix row pins 26.9.1.

@singhpratech
singhpratech deleted the docs/arcadedb-26.9.1-retest branch September 21, 2026 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant