[artile]

Depends on #50 (stacked; the diff includes #49 and #50 until they merge). Refs #48.

Changes

• Snapshot and SchemaDialect gain sqlite (SqliteSnapshot). AnySchemaEntity includes the SQLite entities, so the branch graph, check and snapshot hashing work for SQLite folders unchanged.
• effect-orm generate with dialect: "sqlite" diffs SQLite.table definitions against the folder and writes <timestamp>_<name>/migration.sql and snapshot.json. The SQL is split by --> statement-breakpoint, each statement under a -- <label> comment. SQLite never gets a migration.json.
• New diffSqliteSchemas and SqliteMigrationOp (/schema):
  • CREATE TABLE, DROP TABLE (needs confirm_data_loss).
  • ALTER TABLE ADD COLUMN when SQLite allows it: nullable or a literal default, not in the key or a UNIQUE constraint.
  • ALTER TABLE DROP COLUMN (needs confirm_data_loss) unless the column is in the key or a UNIQUE constraint.
  • Every other change (type, nullability, default, primary key, UNIQUE, a column ADD COLUMN cannot add) is one rebuild_table op: PRAGMA foreign_keys=OFF, CREATE TABLE "__new_<t>", INSERT ... SELECT of the shared columns, DROP TABLE, ALTER TABLE ... RENAME TO, PRAGMA foreign_keys=ON, then the table's indexes again. This is drizzle-kit's form of SQLite's documented procedure.
  • DROP INDEX / CREATE [UNIQUE] INDEX.
  • ALTER TABLE ... RENAME TO and RENAME COLUMN only from a confirm_rename hint. Hint accepts kind: "table" | "column" next to "enum_value". A hint that does not fit both schemas is reported as unsupported.
• generate --baseline --from-drizzle reads a drizzle-kit 1.0 SQLite snapshot.json (version 7) with the new fromDrizzleSqliteSnapshot: tables, columns, keys, indexes, UNIQUE constraints. Anything else (foreign keys, checks, views, generated or AUTOINCREMENT columns, partial indexes) is listed and nothing is written. dialectOf now reads the dialect a drizzle-kit snapshot names, instead of assuming Postgres.
• /migrate run, status, verify, baseline and resolveStep fail with a MigrateSourceError for a SQLite folder. Without this they would use the ClickHouse ledger.
• Docs: a SQLite section in docs/migrations.md, updates to docs/sqlite.md, docs/reference.md, the README lines and the CLI help, and a minor changeset.

Validation

• bun install --frozen-lockfile, bun run build, bun run typecheck: ok.
• bun run test with a local ClickHouse 26.8.2.7 in Docker: 65 files, 1075 tests passed, 0 skipped. Doc citations ok (26 files), export catalog ok (287 /clickhouse, 205 /postgres, 167 /sqlite), doc examples ok (26 files).
• bun scripts/check-package.ts: ESM and CommonJS consumers ok; the ESM consumer diffs and snapshots a SQLite schema from the tarball.
• src/kit/sqlite-generate.test.ts (16 tests) runs generate in a temporary folder. For each change it applies the migrations in order to :memory: and compares PRAGMA table_info, index_list and index_xinfo with a fresh create of the final schema. Seeded rows must survive. Changes covered: first create, add column, drop column, type, nullability, default, UNIQUE, expression-default column, primary key, index add/drop, table drop, a column a rebuild leaves out, table and column rename.
• The same file applies a generated rebuild migration to a local D1 database (Miniflare), one batch per migration, and checks rows and indexes.
• Adoption: src/kit/__fixtures__/drizzle-sqlite is a folder drizzle-kit 1.0.0-rc.5 generated for short_link and a second table (composite key, defaults, a UNIQUE column). Its source schema is next to it. Baseline, then generate from the equal SQLite.table definitions: no change. One changed index then produces exactly its drop and create.

Scope and limits

• No SQLite runner, ledger or verify (U4); /migrate refuses SQLite folders on purpose.
• The drizzle-kit 0.x layout (meta/_journal.json) is not read; Alchemy refuses it too and points to drizzle-kit up.
• Renames are never inferred. Without a hint, a rename reads as a drop plus an add, and the drop asks for confirmation.
• A rebuild copies only the shared columns. It fails at run time when rows do not fit, for example NOT NULL over existing NULLs or a new NOT NULL column without a default. This matches how a Postgres migration fails.
• PRAGMA foreign_keys=OFF/ON is a no-op inside a transaction. effect-orm models no foreign keys yet, so the pragmas only matter for keys created elsewhere.

Decisions to review

• drizzle-kit 1.0 writes a text primary key without NOT NULL and records notNull: false, so SQLite accepts a NULL key. The importer reads a key column as not null, which is what drizzle-kit means and what SQLite.table writes. A drizzle-created table then matches with no rebuild, but still accepts a NULL key until it is rebuilt for another change. A future verify must treat this case as known.
• confirm_rename for a column takes <new table name>.<old column>, so it composes with a table rename in the same migration.
• The baseline migration.sql is a comment only, as for Postgres. Alchemy sends it in one batch with its own bookkeeping statement.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: c837e1ce-fc56-4cb9-ad0c-048b8ca2edee

Commits

Reviewing files that changed from the base of the PR and between c5fa679 and b6e2067.

Files ignored due to path filters: 1

• bun.lock is excluded by !**/*.lock

Files selected for processing: 49

• .changeset/quiet-sqlite-dialects.md
• .changeset/sqlite-generate.md
• .changeset/sqlite-table-ddl.md
• README.md
• docs/README.md
• docs/migrations.md
• docs/reference.md
• docs/sqlite.md
• package.json
• scripts/check-exports-documented.mjs
• src/ch/compile.ts
• src/ch/dialect.ts
• src/ch/expr.ts
• src/ch/functions/builtin.ts
• src/kit/__fixtures__/drizzle-sqlite/20261025075810_init/migration.sql
• src/kit/__fixtures__/drizzle-sqlite/20261025075810_init/snapshot.json
• src/kit/__fixtures__/drizzle-sqlite/schema.ts.txt
• src/kit/cli.ts
• src/kit/generate.ts
• src/kit/sqlite-generate.test.ts
• src/migrate/run.ts
• src/migrate/source.ts
• src/migrate/verify.ts
• src/schema.ts
• src/schema/ddl-expr.ts
• src/schema/diff.ts
• src/schema/entities.ts
• src/schema/pg-define.ts
• src/schema/snapshot.ts
• src/schema/sqlite-define.ts
• src/schema/sqlite-diff.ts
• src/schema/sqlite-drizzle.test.ts
• src/schema/sqlite-drizzle.ts
• src/schema/sqlite-entities.ts
• src/schema/sqlite-ops.ts
• src/schema/sqlite-render.ts
• src/sql/sql-syntax.ts
• src/sqlite.ts
• src/sqlite/d1.test.ts
• src/sqlite/ddl.test.ts
• src/sqlite/dialect.ts
• src/sqlite/functions.ts
• src/sqlite/shape.test-support.ts
• src/sqlite/sqlite.test-d.ts
• src/sqlite/sqlite.test.ts
• src/sqlite/types.ts
• tests/package-consumer-declarations.mts
• tests/package-consumer.mts
• tsdown.config.ts

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Makisuo]

Thanks! #121 has your commits unchanged plus a migration fuzzer (random schema pairs, run on seeded rows, checked against a fresh create). It found two bugs. First, a rebuild that keeps no column ({c2} → {c0}) wrote no INSERT and deleted every row. Second, replacing every column ({c1,c2} → {c3}) dropped the last column before adding, which SQLite refuses. Both are fixed in #121, along with COALESCE(col, default) for a column made NOT NULL with a default, and a docs warning about ON DELETE CASCADE firing during a rebuild under D1. It's stacked on #120 → #119. Pull the commits here if you prefer, or we'll land the stack.

[Makisuo]

Merged as part of #121 (8eb7200 on main), with your commits kept as they were and review fixes on top. Thank you, @tao-io, this is a great contribution! The SQLite migration generator now ships with the fuzzer and shared core suite running on SQLite and D1.