Records/golang/github.com/glebarez/sqlite/v1.11.0/DB.AutoMigrate

shared with 5 packages — this evidence cannot say whose API it is

Published samples

• github.com/glebarez/sqlite v1.11.0: Run GORM on SQLite with CGO_ENABLED=0, past go-sqlite3's runtime stub error Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWsqlite.Opengorm.Opengorm.DeletedAtgorm.ErrRecordNotFoundgorm.ErrDuplicatedKeygorm.Config.TranslateErrorsql.Opensql.DriversDB.PingDB.AutoMigrateDB.UpdatesDB.UpdateDB.SelectDB.FirstDB.FindDB.UnscopedDB.Creatego 1.26 MIT-0 · 2026-08-14

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-09-15

Failure clusters

• observed PROJECT_TEST Evidence gap ×2 v1.11.0 executionContext=go · os=linux · runtime=go@1.26 DB.AutoMigrate
  Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-07 · Last seen: 2026-09-08
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 v1.11.0 os=linux · runtime=go@1.26 sha256:5299cca1c440…
  assertion 1 failed: dialector struct fields mismatch: DSN=<str>, DriverName=<str> · exit status 1
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30
  Diagnostic re-verification candidate
  Where does this failure start and stop?