liteorm

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.

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.

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.

Use when a struct field must be transformed on the way to and from the database — JSON/gob columns, encrypting or compressing a field at rest — without changing its Go type. The codec:<name> tag + liteorm.org/codec.

Use when storing a whole SQLite database compressed and/or encrypted at rest in a gosqlite vfs/vault container (live, per-transaction durable) — the liteorm.org/dialect/sqlite/vault package; distinct from per-object lob compression and from the lighter OpenEncrypted page cipher.

Use when you need to see/trace executed SQL while developing with liteorm, enable debug logging, or wire liteorm into structured (slog/JSON) logs.

Use when opening a SQLite database with at-rest (transparent page-level) encryption — writing/reading an encrypted file, key handling, reopening, and constraints.

Use when writing explicit typed queries with liteorm's query front-end — predicates, joins, unions, subqueries/EXISTS, streaming, Raw, or the query.Repo CRUD.

Use when starting with liteorm — picking the query (explicit) vs orm (declarative) front-end, opening a backend, doing first CRUD, or wiring transactions.

Use when adding liteorm's embedded database studio (admin GUI) to an app — mounting the http.Handler, registering models for rich introspection, and locking it down.

Use when generating liteorm code — typed columns from a Go type, models from a live DB, typed Go from annotated SQL, the sqlc plugin, or porting gorm tags.

Use when evolving a liteorm schema — AutoMigrate for additive changes, GenerateMigration/Diff for reviewable SQL, the migrate runner (Load/New/Up/Down), or WritePair.

Use when working with Postgres-specific liteorm features — LISTEN/NOTIFY, or typed JSONB and array column operators.