mozilla
Squash some old migrations
We have a bunch of migrations that were played in all envs a long time ago. We should look into squashing them to reduce time spent setting up the database in tests/initial env setup.
┆Issue is synchronized with this Jira Task
Not sure if you noticed this at the time this issue was filed, but if the migration to drop File.reviewed is included it breaks other migrations that relied on the __reviewed accessor, so squashing the old migrations should help with that.
Interesting idea danielquinn.org/blog/collapsing-djangos-migrations/
So far, attempts at squashing have not been successful.
Interesting idea danielquinn.org/blog/collapsing-djangos-migrations/
It screws over anyone with a local database that isn't up to date with master but that's an edge case I guess. I'd be more interested in how "do the same on production" can be done in a safe and preprepared way.
So far, attempts at squashing have not been successful.
were there any attempts, or did we just lose interest because it was high effort for low gain (at the time, at least)?
Found the way https://jacklinke.com/squashing-django-migrations-the-easy-way