Afaik there is no deprecation plan for *db_index*, and I doubt it would be since it would require lots of projects to update their models for no particular gain. Probably best to think of *db_index* as a shortcut for adding an index to *Meta.indexes*.
On 28 January 2017 at 21:45, Vitaliy Kucherivaiy <[email protected]> wrote: > Hi Everyone, > > Do I understand this correctly - now there are 2 ways to make a single > field indexed in database: > - FieldClass(db_index=True) > - Model.Meta.indexes > > will it stay like this for future release or 1st approach will be > deprecated/removed later ? > > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/58719258-8ba3-4f9d-9042- > b2003786ec2a%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/58719258-8ba3-4f9d-9042-b2003786ec2a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Adam -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1sEsc7L0VTE%3D%3DqrxAzDQWS1UnSJzNP_jg6%2BfBC0mTY8w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
