On donderdag 24 mei 2018 00:31:57 CEST Benjamin Schollnick wrote:
> Okay, squashing seems to have resolved this issue...
Did you find any issues with the documentation on squashing?
> Seems a bit voodoo-ish, but it worked. Any suggestions for preventing this
> in the future would be nice!
It's voodoo-ish cause you stopped analyzing the problem and went for the work-
around.
So my best guess is:
- The two 0018 migrations were caused by 2 different branches in the source
repository, adding migrations in parallel
- These were applied to the database also in parallel
- Further migrations were added, depending on the 0018 migrations
- One migration was removed that was the common ancenstor for one of the 0018
migrations and another migration.
Without reconstructing the dependency graph it will be difficult to see how you
could have solved it.
To prevent it, establish a protocol for your developers to communicate with
eachother when adding and removing migrations.
--
Melvyn Sopacua
--
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+unsubscribe@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/1555096.CvhEgTB1t9%40fritzbook.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment