메뉴
Use when connecting liteorm to a remote quicSQL server (quicsql.net) instead of a local SQLite file — the sqlite.Open "quicsql://" DSN, sqlite.WrapDB for mTLS/keyring auth, and which SQLite features work over the wire.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when storing large or growing binary content (files, uploads, blobs) in SQLite as streamed io.ReaderAt/io.WriterAt instead of loading whole []byte — the orm.LOB field + liteorm.org/dialect/sqlite/lob.
Use when working with liteorm's declarative orm front-end — model structs and tags, AutoMigrate, the orm.Repo, associations (Load/Attach), hooks, or soft delete.
Use when liteorm code behaves unexpectedly, or proactively before writing it, to avoid the common gotchas around loading, soft delete, types, and dialect-gated operators.
Use when migrating a gorm codebase to liteorm — running models on gorm tags as-is, rewriting them to native orm tags, and adjusting for what differs.
Use when adding vector (sqlite-vec), full-text (FTS5), or hybrid RRF search to liteorm's SQLite backend.
Use when capturing, applying, inverting, or concatenating SQLite changesets (the SESSION extension) for audit logs, one-way replication, or undo — the liteorm.org/dialect/sqlite/changeset package. SQLite backend only.
| name | quicsql |
| description | Use when connecting liteorm to a remote quicSQL server (quicsql.net) instead of a local SQLite file — the sqlite.Open "quicsql://" DSN, sqlite.WrapDB for mTLS/keyring auth, and which SQLite features work over the wire. |
quicSQL (quicsql.net) is a remote SQLite server. LiteORM reaches it through the ordinary liteorm.org/dialect/sqlite backend — same models, same query/orm API, same normalized errors — by opening a quicsql:// DSN instead of a file path. Local (in-process, via gosqlite.org) and remote share one dialect; only the DSN differs.
sqlite.Open dispatches by DSN shape: a bare path / :memory: / file: URI is in-process; any other scheme:// DSN is remote. Blank-import the driver once to register the scheme.
import (
_ "quicsql.net/client/sqldriver" // registers the quicsql:// scheme
"liteorm.org/dialect/sqlite"
)
db, err := sqlite.Open("quicsql://host:7777/app?transport=h2&token=…")
Then everything is the normal SQLite backend: orm.AutoMigrateAll, orm.Repo, the query builder, transactions (SAVEPOINT-nested Begin), introspection, and migrations run server-side; constraint errors normalize to liteorm.ErrUniqueViolation etc.
A DSN can't carry an mTLS cert or ed25519 keyring. Build the *sql.DB with the quicSQL client and wrap it:
db := sqlite.WrapDB(sql.OpenDB(sqldriver.OpenConnectorClient(qc))) // qc is a *client.Client from quicsql.net/client
sqlite.WrapDB(db *sql.DB, opts ...liteorm.Option) *liteorm.DB is the seam Open uses internally. sqlite.RawDB(sess) returns the underlying *sql.DB of a remote session.
vec0/fts5 sidecars on the server (server must have vec0 registered; fts5 is built in).Capture/Apply/Invert/Concat) — SESSION extension, server-side.lob.WriteFrom / ReadAll / Size / Drop.lob.Open/Read/Truncate, native io.WriterAt/io.ReaderAt) does not work remotely — over the wire, blobs move whole. Use a local DB (Open/OpenEncrypted/vault) for partial/streaming blob I/O.quicsql:// scheme isn't registered and Open fails.h1, h2c, insecure=1); use transport=h2/h3.vec0 registered on the server; you don't register it client-side.Open, WrapDB, RawDB). Guide: docs/guides/quicsql.md.