#19441 is the ticket where it was decided that unique=True implies a database index. The documentation says,
"Note that when ``unique`` is ``True``, you don't need to specify`Field.db_index`, because ``unique`` implies the creation of an index." Unless we decide that is wrong, I think the correct condition to solve the issue would be more like `field.db_index or field.unique and field.db_index is not False`. We might also have to change the default keyword of Field from False to None so we know the difference between "unspecified" and False. On Wednesday, April 15, 2015 at 12:39:53 PM UTC-4, Some Developer wrote: > > On 15/04/15 03:37, Curtis Maloney wrote: > > Was the OP referring to the unique index, or the index created for the > > LIKE lookups? > > > > I was involved in a discussion recently [was there something on list > > too?] wanting to be able to opt-out of the second index because they > > knew they didn't need it, and it was _huge_ on their database. > > > > -- > > C > > > > The index created for the LIKE lookups. > > The index name even has _like appended on to the name so I'm pretty sure > that this is the problem at hand. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c77a48fb-470c-47f6-94b5-cff1fdbfbe17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
