Yes, exactly. Django doc tells they do the same. And they do, but if you do not specify db_index=False in field, both indexes are created.
Here is exaplanation : https://stackoverflow.com/questions/53966256/django-db-index-true-not-creating-index-but-class-meta-indexes-yes El domingo, 30 de diciembre de 2018, 0:37:20 (UTC+11), Jason escribió: > > django automatically creates an index for foreign key columns, unless you > specify db_index=False for that field. > > what I suspect is happening here, you're telling django that it should > have two indices for that particular column covering identical areas of > responsibility. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/53c6a572-b860-4195-bede-12af7085dea5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
