Squashing Migrations

[winsmith]

Please summarize your feature request

Over the years, my project has accumulated hundreds of migrations, and I'd like to combine them into as few as possible.

Describe the functionality you're seeking in more detail

Django's ORM has this fantastic concept of squashing migrations where you can combine existing migrations into just one. This speeds up development and removes log clutter during tests.

I'd love to have this functionality in Fluent as well. I don't think it's possible to automatically create squashed migrations, but just replacing 100 migrations that add or modify a field each on my model with just one migration would be awesome.

Have you considered any alternatives?

I've considered just writing new migrations and removing the old ones, but I'm unsure how the metadata stored in the _fluent_migrations table would deal with this. Are there any hidden dangers of just replacing the migrations?

[gwynne]

You can just remove the old migrations if you want to; their presence in the migrations table won't destabilize anything if they aren't present in the code. The primary reason to keep them around is if you ever needed to revert them, which of course requires the logic to be present. If that's not a concern, just deleting them does no harm.

[winsmith]

Oh cool, good to know!