A giant transaction in a post migration can be very risky. This splits the large amount of work this migration needs to do into 2 parts: 1. A re-runnable cleanup job prior to transaction 2. A minimally sized transaction to add the database constraint This avoids large amounts of churn on the table |
||
|---|---|---|
| .. | ||
| fixtures | ||
| migrate | ||
| post_migrate | ||
| api_test_seeds.rb | ||