메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | changesets |
| description | 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. |
Import liteorm.org/dialect/sqlite/changeset. A changeset is a compact binary ([]byte) diff of the rows a set of statements touched. Capture one, invert it, concatenate it, or apply it to another database with a Go conflict handler. Classic uses: audit logs, one-way replication, undo. SQLite-only — every function takes a liteorm.Session opened by liteorm.org/dialect/sqlite.
Capture records every mutation a function makes to the listed tables and returns the serialized changeset. The mutations MUST run against the session Capture hands back (s), not the outer handle — it pins a dedicated connection so the recording and the writes share one physical connection. This is the #1 mistake.
import "liteorm.org/dialect/sqlite/changeset"
cs, err := changeset.Capture(ctx, db, []string{"users", "orders"},
func(ctx context.Context, s liteorm.Session) error {
_, err := s.ExecContext(ctx, `UPDATE users SET name = ? WHERE id = ?`, "Ada", 1)
return err // writes go through s, never db
},
)
Pass a nil/empty table slice to record every table that has a primary key. cs is a []byte — store it, ship it, or apply it elsewhere.
err := changeset.Apply(ctx, replica, cs) // no handler: any conflict aborts the whole apply
Resolve conflicts row by row with WithConflictHandler(func(ConflictType) ConflictAction):
err := changeset.Apply(ctx, replica, cs,
changeset.WithConflictHandler(func(t changeset.ConflictType) changeset.ConflictAction {
switch t {
case changeset.ConflictNotFound:
return changeset.Omit // skip this change
case changeset.ConflictData:
return changeset.Replace // overwrite the target row
default:
return changeset.Abort // abort the whole apply
}
}),
)
ConflictData, ConflictNotFound, ConflictConflict, ConflictConstraint, ConflictForeignKey.Omit, Replace, Abort.WithTableFilter(func(table string) bool) restricts which tables the changeset applies to.undo, err := changeset.Invert(ctx, db, cs) // applying undo reverses what cs did → an undo log
combined, err := changeset.Concat(ctx, db, csA, csB) // as if csB were recorded right after csA
Capture that don't use the handed-back session are silently not recorded.docs/guides/sqlite-changeset.md.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 instrumenting liteorm with metrics, tracing, or audit around every executed statement — the Observer seam (liteorm.WithObserver + QueryEvent). Distinct from slog statement logging (the logging skill), which rides the same seam.