On 15 August 2014 13:13, Collin Anderson wrote:
> You rock, Andrew.
>
+1
>
> On Thu, Aug 14, 2014 at 10:48 PM, Andrew Godwin
> wrote:
> > Solved it now! For those interested, deconstruct() was not including
> > related_name, with the result that
You rock, Andrew.
On Thu, Aug 14, 2014 at 10:48 PM, Andrew Godwin wrote:
> 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
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,
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