#24435: Removing blank=True, null=True from ManyToMany field causes data
deletion
in migration
-------------------------------------+-------------------------------------
Reporter: marktranchant | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8beta1
Severity: Release blocker | Resolution:
Keywords: m2m migrations | Triage Stage: Accepted
deletion blank null |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* severity: Normal => Release blocker
* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.7 => 1.8beta1
* needs_docs: => 0
* stage: Unreviewed => Accepted
Comment:
Seems to be a regression in 1.8 as 1.7 creates a single `AlterField`
operation.
--
Ticket URL: <https://code.djangoproject.com/ticket/24435#comment:1>
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.c0e23f1d021c3dbafb396a460627c076%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
