#24513: "... has no field named None" with M2MField when migrating
-------------------------------------+-------------------------------------
Reporter: Kondou-ger | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution: fixed
Keywords: migrations, bug | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Markus Holtermann <info@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"0385dad073270c37f8c4a5f13edce43f2a69ba8a" 0385dad]:
{{{
#!CommitTicketReference repository=""
revision="0385dad073270c37f8c4a5f13edce43f2a69ba8a"
Fixed #24513 -- Made sure a model is only rendered once during reloads
This also prevents state modifications from corrupting previous states.
Previously, when a model defining a relation was unregistered first,
clearing the cache would cause its related models' _meta to be cleared
and would result in the old models losing track of their relations.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:26>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.bb6b698f091756f9df7fe512e193f582%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
