SQLite Without Migrations Is Still a Toy

你刚刷到这条消息，本来准备顺手划走，但又怕自己错过了真正会影响下一步判断的那一点。

最容易做错的，是sqlite-utils 4.0, now with database schema migrations；代价往往是如果只盯表面热闹，你很容易在错误方向上花掉时间、预算和注意力。；我先给一个保守判断：SQLite没迁移，才只是玩具。

Picture the moment: you see "sqlite-utils 4.0, now with database schema migrations," assume it is just another release note, and move on. That is how people burn time, budget, and attention on the wrong signal. My blunt read: SQLite without migrations is still a toy.

Why say that?

Because the headline matters less than what it changes in practice. In the 4.0 docs published on 2026-07-07, migrations were listed as one of the three major new features. "Migrations" just means a repeatable way to change table structure without relying on memory, manual edits, or a README checklist.

The useful part is how sqlite-utils does it. Migrations are written as Python functions, and the tool records which ones already ran, so rerunning skips what was already applied. That is the line between "a disposable file I poked at" and "a database other people can safely touch." Don't judge an update by how many features it lists. Judge it by whether it changes your next decision.

Boundary matters: I would not force this on every throwaway script, and this is based on the migration docs published on 2026-07-07, not production benchmarks. But if a SQLite file will be edited, deployed, or shared more than once, manual table changes are the amateur move.

真正该讨论的是：sqlite-utils 4.0, now with database schema migrations