Solved it now! For those interested, deconstruct() was not including related_name, with the result that both a ForeignKey and a ManyToMany had the same related_name, and it turns out that Django really doesn't like this, and there's a reason model validation complains about it.
Andrew On Thu, Aug 14, 2014 at 6:57 PM, Collin Anderson <cmawebs...@gmail.com> wrote: > Hi All, > > If anyone's looking for ways to help get 1.7 out the door, there's a > strange but reproducible many-to-many ORM bug happening in migrations. We > could use some help narrowing down the cause of it. > > https://code.djangoproject.com/ticket/23288 > > Thanks, > Collin > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/f1007cbb-6242-4a36-8f79-c58c218b6f37%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/f1007cbb-6242-4a36-8f79-c58c218b6f37%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFwN1uojCuzzDzrgT8Qbztaa_zf%3DgvmNrMsM8TC3e_2%2BqPxHMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
