샘플
gorm.io/gorm 1.31.2: Run GORM on SQLite with CGO_ENABLED=0, past go-sqlite3's runtime stub error
검증된 샘플 — golang gorm.io/gorm 1.31.2: Run GORM on SQLite with CGO_ENABLED=0, past go-sqlite3's runtime stub error. go 1.26 · linux alpine/x64 · docker에서…
sha256:c3632f2f8dc28bb7ef59c80bcd728225b10ed65370fcd4c71af75032848b2f02
이 네트워크가 제공하는 것은 하나입니다. 빌드되는 샘플. 샌드박스에서 돌리고 서명된 영수증을 보관합니다. 등급을 매기지 않고 무엇도 보증하지 않습니다 — 같은 코드가 당신 환경에서 빌드되는지는 측정한 적이 없습니다.
통과한 계약 영수증을 낸 서로 다른 서명 키의 수입니다. 하나면 작성자 혼자이고, 둘 이상이면 다른 사람도 빌드했다는 뜻입니다. 키는 스스로 만드는 것이고 뒤에 등록된 신원이 없으므로, 세는 것은 사람이 아니라 키입니다.
MIT-0
실행 증거
선언된 환경과 서명된 실행을 분리해 두었습니다. 이 샘플이 무엇을 어디서 실행했는지 그대로 볼 수 있습니다.
- 증거 기준
- 서명된 컨트랙트 통과
- 검증 영수증
- 2
- 빌드한 서명 키
- 2
선언된 환경
go 1.26 linux · musl x64 go 1.26 go go
검증 실행 환경
| 환경 | 컨트랙트 | 단계 | 실행일 |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-14 |
| go 1.26 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-18 |
케이스
HOW- 목표
- Run GORM on SQLite with CGO_ENABLED=0, past go-sqlite3's runtime stub error
- 패키지
- 심벌
-
- sqlite.Open
- gorm.Open
- gorm.DeletedAt
- gorm.ErrRecordNotFound
- gorm.ErrDuplicatedKey
- gorm.Config.TranslateError
- sql.Open
- sql.Drivers
- DB.Ping
- DB.AutoMigrate
- DB.Updates
- DB.Update
- DB.Select
- DB.First
- DB.Find
- DB.Unscoped
- DB.Create
- 환경
- go 1.26
- 생성일
- 2026-08-14T13:23:54Z
컨트랙트
- 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
파일
- csx.json
- go.mod
- go.sum
- src/cgo_off.go
- src/cgo_on.go
- src/store.go
- test/main.go