Agreed. We could also add some warnings if there are possible duplicate indexes, for instance in your example, the index only on column1 may not be necessary since the composite index can be used for queries on column1. @ Albert : One question though, I consider that almost all "reverse" fields of O2M fields should be indexed since every read on the "main" record will become slow after a time (e.g. account.move->lines). What do you think ?
|2016-07-29 09:46:44||jcavallo||set||messageid: <firstname.lastname@example.org>|
|2016-07-29 09:46:44||jcavallo||set||recipients: + ced, albertca, pokoli|
|2016-07-29 09:46:44||jcavallo||link||issue5757 messages|
Showing 10 items. Show all history (warning: this could be VERY long)