Sample
Prove that oversized SQLite INTEGER values are no longer silently truncated when decoded into `i32`.
sha256:fe04c033ed20a4aa8fe422091e4de537956a26f01ac407972d1d2f10721268b1
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that oversized SQLite INTEGER values are no longer silently truncated when decoded into `i32`. HOW
- Packages
- sqlx 0.8.6
- Environment
- rust
- Created
- 2026-08-16T11:20:04Z
Commonly assumed
A value larger than `i32::MAX` can still be decoded into `i32`, with SQLite-like truncation happening behind the scenes.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert that reading a SQLite `INTEGER` value greater than `i32::MAX` into `i32` returns an error
- assert that the same value decodes successfully into `i64` so the test fixture is valid
Files
- Cargo.lock
- Cargo.toml
- NOTES.md
- csx.json
- src/lib.rs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- rust 1 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · cargo@1 · 2026-08-16 · ed25519:d91480838ac982c9