메뉴
Use when working with Postgres-specific liteorm features — LISTEN/NOTIFY, or typed JSONB and array column operators.
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 | postgres-advanced |
| description | Use when working with Postgres-specific liteorm features — LISTEN/NOTIFY, or typed JSONB and array column operators. |
Import liteorm.org/dialect/postgres. These features require a session opened by postgres.Open(ctx, dsn). The JSONB/array operators are gated by dialect features, so building them against another backend fails loudly at build time.
Notify sends on any pooled connection; Listen acquires one dedicated connection (LISTEN is connection-scoped) and Receive blocks for messages.
// Publish
_ = postgres.Notify(ctx, db, "jobs", "payload-string") // channel + payload bound, not interpolated
// Subscribe
l, err := postgres.Listen(ctx, db, "jobs") // *Listener; sess must be a *liteorm.DB
defer l.Close(ctx) // UNLISTEN + return conn to pool
for {
n, err := l.Receive(ctx) // blocks; err == ctx.Err() on cancel
if err != nil { return err }
use(n.Channel, n.Payload, n.PID) // postgres.Notification{Channel, Payload string; PID uint32}
}
l.Add(ctx, "more") / l.Remove(ctx, "ch") adjust subscriptions on the same connection. A Listener is not safe for concurrent use — run one Receive loop per listener.
query.JSON("col") drills into object keys, then compares the extracted text or tests containment. Keys and values are always bound parameters.
import "liteorm.org/query"
query.JSON("data").Key("city").Eq("Paris") // ->> path, text compare
query.JSON("data").Key("address").Key("city").Eq("Paris") // nested: chain Key
query.JSON("data").Key("role").In("admin", "owner") // Eq Ne Like In
query.JSON("data").Contains(map[string]any{"active": true}) // jsonb @> (value JSON-encoded)
Path extraction (Eq/Ne/Like/In) works on SQLite too; Contains (@>) is Postgres-only.
query.Array[E]("col") for a Postgres array column — all operators are Postgres-only.
query.Array[string]("tags").Contains("go", "db") // col @> ARRAY[...] (has all)
query.Array[string]("tags").ContainedBy("go", "db") // col <@ ARRAY[...]
query.Array[string]("tags").Overlaps("go", "db") // col && ARRAY[...] (shares any)
query.Array[string]("tags").Has("go") // 'go' = ANY(col) (membership)
Use them in a normal Filter:
query.Select[Doc](db).Filter(query.Array[string]("tags").Has("go")).All(ctx)
Listen needs a *liteorm.DB opened by dialect/postgres — it returns an error otherwise.Close a Listener to UNLISTEN and release the dedicated connection.Contains and all array operators are Postgres-only; the query builder rejects them at BUILD time on other dialects (a clear error, not bad SQL). Plain JSON path extraction is the exception and works on SQLite.