#28052: Django inadvertently removes all indexes when switching to
db_index=False
-----------------------------------+------------------------------------
Reporter: Markus Holtermann | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.11
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"663e48947ff8ef3e6a6275bda2d1ee1b0de13be3" 663e4894]:
{{{
#!CommitTicketReference repository=""
revision="663e48947ff8ef3e6a6275bda2d1ee1b0de13be3"
Fixed #28052 -- Prevented dropping Meta.indexes when changing db_index to
False.
Thanks Marc Tamlyn for the report and Ian Foote/Tim Graham for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28052#comment:3>
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.ff41ad8fa4ac69029a457003f4432a94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
