#24435: Removing blank=True, null=True from ManyToMany field causes data
deletion
in migration
-------------------------------------+-------------------------------------
Reporter: marktranchant | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.8beta1
Severity: Release blocker | Resolution: fixed
Keywords: m2m migrations | Triage Stage: Ready for
deletion blank null | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Markus Holtermann <info@…>):
In [changeset:"bff446c205e0c4d436a5147906397ab7534343f3"]:
{{{
#!CommitTicketReference repository=""
revision="bff446c205e0c4d436a5147906397ab7534343f3"
[1.8.x] Fixed #24435 -- Prevented m2m field removal and addition in
migrations when changing blank
Thanks Mark Tranchant for the report and Tim Graham for the test and
review.
Backport of a9e29fae105d1ddd4e0ac2059cbe62b0ee348bc8 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24435#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/071.ca4bde783e66171ffc761dced1570ca9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
