Removing squashed migrations prevents migration

[jribbens]

Because the migrations have been squashed, migration is impossible as it returns the following error: django.db.utils.ProgrammingError: relation "reversion_revision" already exists... you have to pip install django-reversion==3.0.1 && ./manage.py migrate reversion && pip install -U django-reversion

If there were only 4 of them and somehow having both the originals and the squashed one causes problems, why not just remove the squashed one and keep the originals?

[etianen]

Once a set of migrations have been squashed, they cannot be un-squashed without breaking existing projects. It's too late.

It should work to upgrade to 3.0.0, run migrate, then upgrade to 3.0.5, then migrate again.

[m4rk3r]

Perhaps this could be better called out in the changelog for those of us upgrading from old versions? @jribbens solution (uninstall, install 3.0.1, migrate, upgrade) worked

[etianen]

Happy to take a MR to add a note to the changelog.

…

On Wed, 29 Apr 2020 at 18:18, mark beasley ***@***.***> wrote: Perhaps this could be better called out in the changelog for those of us upgrading from old versions? @jribbens <https://github.com/jribbens> solution (uninstall, install 3.0.1, migrate, upgrade) worked — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#822 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABEKCGMBLUSDXQOOI7MV4DRPBOMTANCNFSM4KV3O5YA> .