#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
--------------------------------------+------------------------------------
Reporter: Thomas Recouvreux | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: migrations m2m mysql | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by JR Heard):
* status: assigned => new
* owner: Shun Yu => (none)
Comment:
The issue in this ticket is still happening for me on Django 2.1.9 on
Postgres. Adding `blank=True` to a `ManyToManyField` drops the FK
constraints on the join table and creates them back, exactly as described.
This ticket hasn't been touched in a couple of years so I'm going to
deassign it. I hope this is the right thing to do here, I'm new to the
Django community :)
--
Ticket URL: <https://code.djangoproject.com/ticket/25253#comment:16>
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/066.958f03765d1ab6189e6b1aa483b43f97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
