Repository navigation
chore: upgrade to HawDB 0.30 and qualify row-page v2 - #11
Merged
Merged
Conversation
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
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.
Summary
HawDB 0.30 replaces fixed-slot relational row pages with exact-length v2 pages and explicitly refuses v1 checkpoints. The dialect's previous cross-version reopen claims no longer describe the engine's storage contract.
0.30.0withhawdb>=0.30.0,<0.31.0, including package metadata, dependency hints, source builds, published-wheel CI, and documentation.PGTypeCompiler/PGIdentifierPreparerreuse and the existing timestamp/Decimal reflection. Python DB-API and relational SQL interfaces are unchanged from 0.29; no speculative compiler or connection options are needed.StorageError(kind="unsupported_storage_format")through SQLAlchemy'sDBAPIError, with all.hawdbfile digests unchanged.Compatibility
This does not migrate or recreate any user database. Existing databases containing v1 row-page manifests must be exported using their matching old reader and imported into a separately recreated 0.30 database. Metadata open alone does not prove branch data admission. The README replaces the old direct-upgrade promise with this explicit boundary and preserves the driver's typed error.
The new
JSON_VALUE(... NULL ON NONSCALAR)syntax is Cypher-only. The LlamaIndex graph store and Bun FFI adapter are separate integrations; graph optimizer and search changes do not require dialect flags.Related changes
2d814740161f7e5cba0527ab3b1427d6eb8ac08bValidation
f0996a4ecb4c487404b2653f1aed0be9416279b3.2d814740161f7e5cba0527ab3b1427d6eb8ac08b; the PyPI lane independently downloadedhawdb-0.30.0-cp311-abi3-manylinux_2_28_x86_64.whl. Tested SQLAlchemy versions are 2.0.57 and 2.1.8.This is the project's targeted compatibility suite, not the full SQLAlchemy external-dialect suite or all storage/platform configurations. No package publication is performed by this PR.