#24670: Django migrations are not scaling well with number of operations in
migration
-------------------------------------+-------------------------------------
Reporter: kurevin | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage:
optimization | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by MarkusH):
Hi kurevin, according to the trace you gave above this looks like #24591
which is about to be committet to master and in a slightly modified form
to stable/1.8.x.
Regarding the backports to 1.7: there are two reasons those changes are
not being backported:
1. in 1.8 we now cache the project state across migrations as much as
possible and due to API changes many patches are not easy to be backported
2. 1.7 only receives security and data loss related fixes.
--
Ticket URL: <https://code.djangoproject.com/ticket/24670#comment:3>
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/065.b95bc0c9993753c4ccf5caf591c455f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
