#24513: "... has no field named None" with M2MField when migrating
---------------------------------+------------------------------------
Reporter: Kondou-ger | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8rc1
Severity: Normal | Resolution:
Keywords: migrations, bug | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by patrys):
I have found the reason of the crash.
It turns that if a model has a relation to itself,
`ProjectState.reload_model` will place it twice on the
`states_to_be_rendered` list. This causes all relations to point to the
registered version of the model (and later cause problems where they are
unable to find their reverse relationship which leads to the field name
being set to `None`).
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:13>
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.69f2f5208f9218963912e0b4266c4b97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
