#24563: Migration for M2M Field fails with FieldDoesNotExist when removing
null=True from model
-------------------------------------+-------------------------------------
Reporter: GitRon | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: migrations, | Triage Stage:
many2many, nullable | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by MarkusH):
Is this on the 1.8.x development branch or the 1.8.0 release. We fixed a
few bugs in the upcoming 1.8.1 release:
https://docs.djangoproject.com/en/dev/releases/1.8.1/
Specifically #24513 and #24573 come to mind.
--
Ticket URL: <https://code.djangoproject.com/ticket/24563#comment:7>
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/064.e6aa9564fa576bf8a9e517c8adc1c7d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
