#23738: Migrations broken with django 1.7.1 when changing null from true to
false.
---------------------------------+------------------------------------
Reporter: niwibe | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"40ad022d5e366f56424dcdb885607d13c00a550e"]:
{{{
#!CommitTicketReference repository=""
revision="40ad022d5e366f56424dcdb885607d13c00a550e"
[1.7.x] Fixed #23738 -- Allowed migrating from NULL to NOT NULL with the
same default value
Thanks to Andrey Antukh for the report.
Backport of 715ccfde24 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23738#comment:12>
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.a045fc6beef314549ffcb7de86510216%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
