#24513: "... has no field named None" with M2MField when migrating
---------------------------------+--------------------------------------
Reporter: Kondou-ger | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.8rc1
Severity: Normal | Resolution:
Keywords: migrations, bug | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by MarkusH):
I think the unique_together constraint is part of the m2m through table
which is automatically created by Django (which is `<class
'__fake__.User_groups'>`). The odd thing, the field `None` should be
`user` (FK from the m2m through table to your user model table). I have no
idea yet why or where the name resolution fails / the field cache isn't
cleared.
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.aca9378c590f09c107c90ab7f7770863%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
