Simon Pinfold 195045d257 docs(db): restore the rationale for locking before migration ...

Commit 1dbcdcd7 and the comment-cleanup pass 8205022f reduced this to "All
database reads and writes, including the legacy import, run under the lock",
dropping the part that did the work: upstream master locks after migrating and
justifies it with "Alembic uses its own connection, so we must wait until it's
done before locking -- otherwise our own lock blocks the migration". That is
false, the lock is on a separate <db>.lock file, and the surviving sentence
said nothing to stop a contributor "fixing" the ordering back.

Restored and adapted rather than pasted: the legacy copy and the db_exists
probe now happen inside the lock, which the original text predates, so both
are named in the list of things the ordering makes mutually exclusive.

2026-09-17 19:47:38 -07:00

..

db.py

docs(db): restore the rationale for locking before migration

2026-09-17 19:47:38 -07:00

models.py

feat(assets): align local API with cloud spec (#12863)

2026-03-16 12:34:04 -07:00