#27279: Performance regression when running migrate with RenameModel operations
-------------------------------------+-------------------------------------
Reporter: mtomiyoshi | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: closed
Component: Migrations | Version: 1.10
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"040bd7c9387cfbf70a543c507b3b9eeb8f2725dc" 040bd7c]:
{{{
#!CommitTicketReference repository=""
revision="040bd7c9387cfbf70a543c507b3b9eeb8f2725dc"
Fixed #27279 -- Fixed a migration performance regression related to
RenameModel operations.
Thanks Trac alias mtomiyoshi for the report, Marten Kenbeek for the
initial
patch and Tim for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27279#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/068.80a120d9e00c8e62398440d60e5e3a69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
