Add anti-deadlock instructions to DB update README (#1552)

This commit is contained in:
Ben McIlwain 2022-03-09 18:50:15 -05:00 committed by GitHub
parent c1ba725d3d
commit 13e2b15a9d

View file

@ -56,6 +56,12 @@ following steps:
table statements can be used as is, whereas alter table statements should be table statements can be used as is, whereas alter table statements should be
written to change any existing tables. written to change any existing tables.
Note that each incremental file MUST be limited to changes to a single
table (otherwise it may hit deadlock when applying on sandbox/production
where it'll be competing against live traffic that may also be locking said
tables but in a different order). It's OK to include these separate Flyway
scripts in a single PR.
This script should be stored in a new file in the This script should be stored in a new file in the
`db/src/main/resources/sql/flyway` folder using the naming pattern `db/src/main/resources/sql/flyway` folder using the naming pattern
`V{id}__{description text}.sql`, where `{id}` is the next highest number `V{id}__{description text}.sql`, where `{id}` is the next highest number