sqlite schema-migrations transactions python-first database-tooling

sqlite-utils 4.0 adds schema migrations, nested transactions

Declarative migrations via Python decorators with automatic transaction tracking replace manual ALTER TABLE workarounds and sqlite-migrate dependency.

Summary

Eliminates brittle schema evolution patterns in SQLite projects; db.atomic() context manager makes migrations safer by default and supports savepoint-based nesting. Integrates migration tracking directly into sqlite-utils, consolidating tooling for the Datasette/LLM ecosystem.

Why it matters

Implementation verdict

Ready now. Replaces sqlite-migrate (which is now a compatibility shim) and manual migration scripts. Requires Python-based schema definitions via @migrations() decorators; no ORM model generation like Django. Start with uvx sqlite-utils migrate data.db migrations.py; existing sqlite-migrate code continues to work without changes. The db.atomic() context manager is immediately useful for any transaction-heavy workload.

Sources

1.database migrations, nested transactions (via a new db.atomic() method), and support for compound foreign keys
2.The _sqlite_migrations table is used to keep track of which migration functions have been run
3.sqlite-utils encourages programmatic table creation rather than a model definition ORM
4.I've used that package in enough places now that I'm confident in the design, so I've decided to promote it to a feature of sqlite-utils
5.the 124th release of that project and the first major version bump since 3.0 in November 2020

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs