Squash migrations using the "nuclear" option #634
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Andrew-Dickinson
force-pushed
the
andrew/migrations-squash
branch
from
904dc39
to
8c09599
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #634 +/- ##
=======================================
Coverage 94.03% 94.03%
=======================================
Files 75 75
Lines 3086 3086
=======================================
Hits 2902 2902
Misses 184 184 ☔ View full report in Codecov by Sentry. |
james-otten
approved these changes
Oct 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed all existing migration code, and ran
python src/manage.py makemigrationsto create new ones from scratchCopied over the manually written migration for the readonly database role
Closes #594
Procedure to roll out this change:
Everywhere that we have a DB, drop all the tables (super destructive option, make sure you have a backup first):
And run the new migrations
Then to get the data back, import from a backup, run the import script, use
scripts/import_spreadsheet_dump.sh, etc.