#28339: Setting db_index=False on a field doesn't actually remove the index
----------------------------------+--------------------------------------
Reporter: Craig de Stigter | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.11
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
----------------------------------+--------------------------------------
Changes (by Craig de Stigter):
* status: closed => new
* resolution: invalid =>
Comment:
On second thoughts, this is still a bug, right?
sqlmigrate above shows that the operation creating the indices _knows_ the
name of the indices:
{{{
#!sql
CREATE INDEX "a_b_charfield_a5049317" ON "a_b" ("charfield");
}}}
so clearly this can be predicted up-front by the migration - it shouldn't
need to consult the database to list indices prior to dropping them.
--
Ticket URL: <https://code.djangoproject.com/ticket/28339#comment:6>
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/065.16619654025a39d83631ae25304e9dbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
