according to the documentation models.ForeignKeys creates implicitly an index 
on the underlying database.

Wouldn't it be reasonable to change the default behaviour to only create 
implicit index, if there is no index_together or unique_together starting with 
the name of the foreign key?   In such cases the implicit index is redundant, 
at least with Postgresql, as the value can be found fast using the _together 


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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to