#27500: Warn about potentially significant performance degrading schema changes
when making/running migrations
-------------------------------------+-------------------------------------
Reporter: Code0x58 | Owner: nobody
Type: | Status: new
Uncategorized |
Component: Core | Version: 1.8
(Management commands) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Today we ran a migration which removed a unique=True constraint on a char
field for a MySQL database, this implicitly removed the indexing on the
column which caused significant performance problems.
It didn't take too long to work out the mistake, but it would be nice if
there was more of a fuss made when things like (implicit) index removal
occur.
Hopefully this way developers are less likely to overlook or not be aware
of such things, and also help pinpoint the source of an issue after an
update.
--
Ticket URL: <https://code.djangoproject.com/ticket/27500>
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/051.d1c4a413c44cb2cc4254a79968bad140%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
