Migrations should automatically be wrapped in transactions by default
Migrations that require execution outside of a transaction (e.g. to enable
augmenting non-DDL-safe things, such as ENUM
s in PostgreSQL) should be
explicitly marked
If you want to change selection, open document below and click on "Move attachment"
Unknown titleptable if absolutely necessary Production databases are critical - NEVER RESET Migrating data (as well as DDL) is acceptable, but should be kept to fast operations (or trigger a background job) <span>Migrations should automatically be wrapped in transactions by default Migrations that require execution outside of a transaction (e.g. to enable augmenting non-DDL-safe things, such as ENUMs in PostgreSQL) should be explicitly marked Migrations should not pollute PostgreSQL global settings (e.g. use SET LOCAL rather than SET) Roles should be managed outside of migrations (since they can be shared between databases) Summary
status | not read | | reprioritisations | |
---|
last reprioritisation on | | | suggested re-reading day | |
---|
started reading on | | | finished reading on | |
---|
Details