#24591: Copy ModelState.fields and ModelState.managers instead of cloning.
-------------------------------------+-------------------------------------
Reporter: knbk | Owner: knbk
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: master
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
-------------------------------------+-------------------------------------
Comment (by dalore):
I know this has been marked fixed but how is this fixed? I followed
another ticket to here in which was about the migrations being slow, well
this is what I get after upgrading Django from 1.6 to 1.8 when running
test (To see if everything works):
Running migrations:
Rendering model states...
DONE (1410.571s)
Then it goes on and runs each migration taking 1 - 60 per migrations. How
is 20+ minutes acceptable? This is the time it takes before it even starts
applying the new initial migrations.
This is an old project that started in the early django days, even Andrew
Godwin himself worked on this project for a bit.
--
Ticket URL: <https://code.djangoproject.com/ticket/24591#comment:11>
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/062.417ae6ae980eff3edb6b57dfe36e948b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.