#27500: Warn about potentially significant performance degrading schema changes
when making/running migrations
-------------------------------------+-------------------------------------
Reporter: Oliver Bristow | Owner: nobody
Type: Uncategorized | Status: new
Component: Core (Management | Version: 1.8
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I don't know if it's Django's job to try to predict how schema changes
might impact performance. What's fast for one database might be slow on
another and it also depends on the number of rows. If you have a patch in
mind, we can take a look, but I'm not certain this will be practical.
--
Ticket URL: <https://code.djangoproject.com/ticket/27500#comment:1>
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/066.c8b4cdffcd42fd5d014231f0e828e14f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
