Report duplicate and overlapping database indices

[labkey-adam]

Rationale

New devtools action inspects all indexes in tables in module schemas and flags those with duplicate or overlapping column sets. In most (all?) cases these duplicates are unnecessary, causing bloat and perhaps inefficiency.

Move standard redirect methods and callers away from passing URL strings.

Tasks 📍

• Manual Testing @labkey-danield
  • With the devtools module present, visit tools-begin.view (e.g., http://localhost:8080/home/tools-begin.view)
  • Click the overlappingIndices link
  • Observe and lament how many overlapping indices we have

[labkey-matthewb]

Seems useful. Some overlapping indexes are not redundant. If you want index (RowId, Other) I don't think you can the (RowId) part is unique. So you end up with two indexes.

[labkey-adam]

Seems useful. Some overlapping indexes are not redundant. If you want index (RowId, Other) I don't think you can the (RowId) part is unique. So you end up with two indexes.

@labkey-matthewb see my most recent commit (committed earlier this morning)... it separates out a third group of valid overlaps: any PK or UQ index with a column list that's a subset of a non-unique index's column list. I think those are valid and all others are redundant, but please check my logic.