#23738: Migrations broken with django 1.7.1 when changing null from true to
false.
----------------------------+--------------------------------------
Reporter: niwibe | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by niwibe):
The migration is generated by django 1.7 but I have tried generate it with
django 1.7.1, but it no such effect. The same exception is raised and the
same behavior on creating the migration file (missing null=True and
blank=True on alterfield action).
Also, I have tried with 1.7.2dev (stable/1.7.x branch) and also I have
found the same exception.
--
Ticket URL: <https://code.djangoproject.com/ticket/23738#comment:2>
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.b9cd9fc26776bf01ceb36043eae99a8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
