On Monday 14 March 2016 12:15:33 akki wrote: > > you can't have identical indexes defined in multiple ways with the same > > names. > > Yes, I will be checking for the duplications at the autodetector level > itself. We need to take care that no two indexes are for the same fields, > and none of them have a clashing name. On such an occurrence, we can raise > an error like "Multiple indexes have been set for 'field1' " or merge them > ourself internally (if they mean exactly the same).
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).
