القائمة
Use when using gorm.io/gorm with gosqlite — the gosqlite.org/gorm dialector, a CGo-free drop-in for glebarez/sqlite and gorm.io/driver/sqlite, shipped as its own module.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the task needs a SQL function or virtual table from the gosqlite ext/ catalog — regexp, uuid, hash, ipaddr, zorder, stats, unicode, encode, text, fuzzy, decimal, money, time, eval, csv, lines, statement, closure, pivot, rtree, series, array, bloom, spellfix1, fileio, blobio.
Use when debugging surprising behaviour with gosqlite, or as a pre-ship checklist — the gotchas around per-conn hooks, the connection pool, vec quirks, bind limits, and what is not supported.
Use when the task needs encryption at rest, storing a database compressed at rest, page-checksum corruption detection, an in-memory database with isolation, or serving a database from an embed.FS / byte buffer in a Go app with gosqlite.
Use when switching an existing Go project to gosqlite from mattn/go-sqlite3, modernc.org/sqlite, glebarez/sqlite, gorm.io/driver/sqlite, or ncruces/go-sqlite3.
Use when opening a SQLite database in Go with gosqlite.org, choosing the "sqlite" vs "sqlite3" driver name, or deciding which sub-package to reach for. The starting point for any task using this driver.
Use when storing large, growable, or randomly-writable byte objects (files, uploads, streamed content) in SQLite with gosqlite — the blobstore package, plus when to reach for the fixed-size Conn.OpenBlob / ext/blobio instead.
| name | gorm |
| description | Use when using gorm.io/gorm with gosqlite — the gosqlite.org/gorm dialector, a CGo-free drop-in for glebarez/sqlite and gorm.io/driver/sqlite, shipped as its own module. |
gosqlite.org/gorm is a gorm.Dialector — a drop-in for glebarez/sqlite and gorm.io/driver/sqlite. It is its own module (go get gosqlite.org/gorm); the gosqlite core does not depend on gorm.
import (
"gorm.io/gorm"
sqlite "gosqlite.org/gorm" // package is `sqlite` — drop-in for glebarez/sqlite + gorm.io/driver/sqlite
)
db, _ := gorm.Open(sqlite.Open("file:my.db?_pragma=foreign_keys(1)"), &gorm.Config{})
The package name is sqlite, so existing glebarez / go-gorm call sites compile unchanged: sqlite.Open(dsn) and sqlite.New(Config{...}) both exist.
For the modern typed config, also import the root gosqlite.org (also package sqlite) and alias the dialector sqlitegorm:
import (
sqlite "gosqlite.org"
sqlitegorm "gosqlite.org/gorm"
)
db, _ := sqlitegorm.OpenConfig(sqlite.Config{Path: "my.db", Pragmas: sqlite.RecommendedPragmas()})
OpenConfig returns a *sqlitegorm.DB that embeds *gorm.DB; defer db.Close() drains the pool — no separate *sql.DB teardown.vfs/crypto itself.gorm.ErrDuplicatedKey, foreign-key violations to gorm.ErrForeignKeyViolated.time.Time columns: the dialector injects _texttotime=1 so DATE / DATETIME / TIMESTAMP scan back as time.Time; opt out with _texttotime=0 in the DSN.csv, lines, closure, bloom, spellfix1, …) work through gorm: register the module on the pool, pin it with sqlDB.SetMaxOpenConns(1), create the vtab with db.Exec (AutoMigrate can't emit CREATE VIRTUAL TABLE), then read with db.Raw / db.Table(...).Scan. See gorm/examples/ext-vtabs.Runnable demos: gorm/examples/ (getting-started, from-glebarez, vfs, ext-scalars, ext-vtabs).