Dear Django users,
I was playing a bit with migration squashing, and found that, after applying a
squashed migration (following the guide), stale records are left in the
migration history, which will prevent another migration to be applied with the
same name. This effectively results in a different state when applying
migrations step-by-step, and when applying from the squashed migrations.
I've created a test project: https://github.com/rkojedzinszky/django-squash-bug
First, one should migrate each commit step-by-step, and on another
installation, just at the last commit. I assume the result should be identical,
but unfortunately the asd.Model1 tables remain different in the two test cases.
Is this a bug, or feature?
Regards,
Kojedzinszky Richárd
Euronet Magyarorszag Informatika Zrt.
