#24828: AlterUniqueTogether prevents squashmigrations optimizations
-------------------------------+--------------------------------------
Reporter: riklaunim | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.8
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
-------------------------------+--------------------------------------
Changes (by riklaunim):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
AlterIndexTogether also. I've also noticed that if there are two or more
models the optimization is quite fragile to order of operations. When I
move all model A simple add/remove/alter operations after CreateModel,
then move similar operations after CreateModel B then it will resquash it
nicely. If those operations are mixes and CreateModel A, B are at start
then it won't merge operations.
--
Ticket URL: <https://code.djangoproject.com/ticket/24828#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/067.93fde0e890d849bdd19702cea79683eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
