#24554: Migrations taking up to an hour to run
-------------------------------------+-------------------------------------
Reporter: ryanahall | Owner: ryanahall
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Markus Holtermann <info@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"57dc8dd3fa3c3adf133c522ecadb501d94bacd52" 57dc8dd3]:
{{{
#!CommitTicketReference repository=""
revision="57dc8dd3fa3c3adf133c522ecadb501d94bacd52"
Fixed #24554 -- Sped up migrations by rendering initial apps when they are
first needed
Calling Migration.mutate_state() now also allows to do in_place
mutations in case an intermediate state is thrown away later.
Thanks Anssi Kääriäinen for the idea, Ryan Hall for parts of the patch,
and Claude Paroz and Tim Graham for the review
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24554#comment:8>
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.c2b4bee8f921563b6410cf33e84339ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
