#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 Kondou-ger):
I attached the diff that created the migration.
Weird thing is, I can't reproduce this either. If I start a fresh app with
all my models in I get a different migration than a squashed on from my
app that produces the bug. Using this created initial migration as a
"squashed" migration even works as a workaround …
I'm doing a git-bisect on my project with django1.8c1 now, to see what
exactly introduced the bug in my project.
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:4>
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.46ee2f4ca7bcc43649939495626ff8ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
