It's a known issue: https://code.djangoproject.com/ticket/26760
On Tuesday, October 4, 2016 at 4:47:36 PM UTC-4, Kojedzinszky Richárd wrote: > > 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. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2167cef4-a910-4d30-9af9-181c2f8b838f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
