Conversation
quinnj
force-pushed
the
feature/incremental-blob-io
branch
from
September 26, 2026 11:05
113eb3b to
e1b1eae
Compare
quinnj
changed the base branch from
master
to
fix/statement-handle-lifetime
September 26, 2026 11:05
This branch has not been deployed
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.
Large SQLite BLOBs currently require whole-value query materialization. Add qualified
SQLite.Blob <: IOso callers can read or overwrite an existing fixed-size value using normal Julia IO and a reusable buffer. It defaults to read-only access, exposes raw BLOB/TEXT bytes, and leaves ordinary query conversion unchanged. No new export or dependency is added.This PR is stacked on #362. BLOB and statement handles share one database lifecycle lock. The DB retains handle references without retaining stream objects; explicit DB close consumes all tracked BLOBs, including those with pending finalizers, so they cannot commit later. GC finalizers defer while the lock is busy. Close errors still consume handles and are reported after cleanup; a do-block preserves both callback and close failures. Ordinary stream/connection use still requires caller synchronization.
Validation on the actual stacked source:
The docs cover fixed-size storage, row expiry, implicit commits, explicit rollback, bounded-buffer IO, and close-error behavior. Incremental IO copies bytes between SQLite and the caller's buffer; whole-value operations remain available. This update makes no new transfer-throughput claim.
Closes #345.
All seven hosted runtime, documentation, and native-core checks pass at
e1b1eae, including public BLOB IO in the Linux x86_64 native executable.Co-authored by Codex