#24743: Django 1.8.1 migrations are actually slower than 1.8?
--------------------------------------+------------------------------------
Reporter: pzrq | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by timgraham):
Should we add this to the 1.8.1 release notes and remove the release
blocker flag?
{{{
#!diff
diff --git a/docs/releases/1.8.1.txt b/docs/releases/1.8.1.txt
index b9fc816..b01b09e 100644
--- a/docs/releases/1.8.1.txt
+++ b/docs/releases/1.8.1.txt
@@ -93,4 +93,5 @@ Optimizations
* Changed ``ModelState`` to deepcopy fields instead of deconstructing and
reconstructing (:ticket:`24591`). This speeds up the rendering of model
states and reduces memory usage when running :djadmin:`manage.py
migrate
- <migrate>`.
+ <migrate>` (although other changes in this release may negate any
performance
+ benefits).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24743#comment:4>
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.a12a885702aaa19f9a216f0daa7daac7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
