Repository navigation
fix(sqlite): upgrade bundled SQLite and checked hooks - #79
Merged
Merged
Conversation
Use SQLite 3.51.3 to fix WAL-reset corruption. Preserve checked unsigned bindings, adopt the supported main-database API and reject hook installation failures before SQL.
This was referenced Oct 15, 2026
forhappy
marked this pull request as ready for review
October 15, 2026 07:21
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.
Cellule currently bundles SQLite 3.49.1, which is affected by the upstream WAL-reset corruption race. Upgrade the ordinary published dependency to rusqlite 0.39 / SQLite 3.51.3 and preserve range-checked unsigned SQL bindings with
fallible_uint.This upgrades current Cellule 0.2 main. The matching minimal backport for Crab's pinned 0.1 revision is #78; Crab can consume that dependency correction without importing the unrelated Node Bundle migration. No merge requested.
Contract adaptation
DatabaseName::Mainwith upstream'sMAIN_DBat incremental blob I/O and read-only-root validation.Evidence and limits
737ae4a34738ffa0c3ff7f9bb18df914dd1cad163f28fd6b6e114a344fe6d618.Review evidence map
aaacf31; only the dependency closure and required API adaptations changeIs this the best fix? Use the maintained upstream SQLite fix and adapt its explicit API contracts. Global cache serialization or private SQLite patches would add ownership complexity and constrain throughput without delivering the same dependency correction.
Primary contracts: SQLite WAL-reset fix, rusqlite 0.39 release, feature authority.