Sample
Run GORM on SQLite with CGO_ENABLED=0, past go-sqlite3's runtime stub error
sha256:c3632f2f8dc28bb7ef59c80bcd728225b10ed65370fcd4c71af75032848b2f02
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Run GORM on SQLite with CGO_ENABLED=0, past go-sqlite3's runtime stub error HOW
- Packages
- gorm.io/gorm 1.31.2 github.com/glebarez/sqlite 1.11.0 modernc.org/sqlite 1.56.0 gorm.io/driver/sqlite 1.6.0 github.com/mattn/go-sqlite3 1.14.49
- Environment
- go 1.26
- Created
- 2026-08-14T13:23:54Z
Contract
- assert the build has cgo off and that there is no C compiler on PATH, so rebuilding with CGO_ENABLED=1 has nothing to invoke
- assert gorm.io/driver/sqlite still compiles and links with cgo off, since the contract binary imports it, and that its stub registers the database/sql driver name sqlite3 alongside the pure-Go engine's sqlite
- assert opening that cgo driver fails only at connection time, with go-sqlite3's Binary was compiled with CGO_ENABLED=0 stub message
- assert sql.Open on sqlite3 returns no error at all, because it does not connect, and that Ping is where the stub surfaces
- assert the linked pure-Go engine reports SQLite 3.53.3, so the forced modernc.org/sqlite pin cannot drift back to what minimal version selection would pick
- assert AutoMigrate creates the table and its deleted_at column, that running it again on an unchanged model is a no-op rather than an error, and that Create writes the auto-increment key back into the struct
- assert Updates with a struct writes the non-zero field and silently omits false and 0, returning no error and RowsAffected 1
- assert Updates with a map writes those same zero values, since a map has no zero value to be confused by
- assert Select names the columns that force a struct's zero values through
- assert Update with an explicit value writes a literal zero
- assert First on a missing row returns gorm.ErrRecordNotFound while Find returns a nil error with RowsAffected 0
- assert gorm.DeletedAt makes Delete an UPDATE: Find and First skip the row, Unscoped finds it with DeletedAt.Valid set, and a raw count shows the row still in the table
- assert reusing the primary key of a soft-deleted row fails with SQLite's own UNIQUE constraint failed: users.id message, which does not match gorm.ErrDuplicatedKey by default
- assert TranslateError makes that same conflict match gorm.ErrDuplicatedKey and replaces the driver error, so the constraint message is gone
- assert two connections to :memory: are two separate databases, so the migrated table is missing on the second one unless the pool is pinned to a single connection
Files
- csx.json
- go.mod
- go.sum
- src/cgo_off.go
- src/cgo_on.go
- src/store.go
- test/main.go
Origin Seeder
Verification receipts
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-14 · ed25519:a2ec939a4c60e243
- · CONTAINER_RUN · compile:SKIPPED · contract:FAIL · load:SKIPPED · resolve:PASS · golang@1 · 2026-08-14 · ed25519:7da3f610facce8bf