> > > That is a bit too strict; sometimes it does make sense to provide more > than > one kind of index on one field. As a trivial example, you may want to > support > case-sensitive uniqueness as well as case-insensitive search (say, for > user- > names). > Ohh yes definitely, I meant no two identical indexes on the same field. Sorry for the wrong choice of words.
-- 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 https://groups.google.com/d/msgid/django-developers/119f21bf-b6fa-480c-a100-d779c7092a5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
