Bind integer parameters as checked SQLite integers - #356
Merged
Merged
Conversation
quinnj
referenced
this pull request
Sep 30, 2026
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Integer parameters other than Int32, Int64, and Bool fell through to Julia serialization and were stored as BLOBs. A query using UInt16(1000) therefore did not match an INTEGER row containing 1000, and strict table loading failed.
Route Integer bindings through checked Int64 conversion in the shared binding method. Values outside SQLite's signed 64-bit range now raise InexactError instead of being serialized. Existing serialized rows remain readable; this change does not migrate them. UDF return serialization is unchanged.
Refs #313.
Validation: the new tests failed before the fix. All 308 tests pass on Julia 1.9.4, 1.12.7, and 1.13.0. Coverage includes 11 integer types, positional and named parameters, SQL equality/storage type, strict-table loading, Int64 limits, and overflow rejection. The original 1000 query also passed across nine integer types.
Co-authored by Codex