G-9203
🆓Warning
Always follow naming conventions for indexes.
Reason
Index names share the same namespace as tables, indexes, views, etc. Follow naming conventions to prevent naming conflicts, improve readability, and clearly indicate the scope without forcing the use of qualified names. A common practice is to use a prefix and/or suffix to distinguish the identifier types.
Recommendations
Indexes serving a constraint (primary, unique or foreign key) are named accordingly.
Other indexes should have the name of the table and columns (or their purpose) in their name and should also have _idx as a suffix.
Example
Non-Compliant Example
create index employees_first_name on employees(first_name);
Issues
| Line | Column | Message |
|---|---|---|
| 1 | 14 | index employees_first_name does not match '^[a-z][a-z0-9$#_]*_(pk|uk\d*|fk\d*|idx)$'. |
Compliant Solution - ★★★★★
create index employees_first_name_idx on employees(first_name);
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| IndexPattern | Case-insensitive regular expression pattern for SQL indexes. | ^[a-z][a-z0-9$#_]*_(pk|uk\d*|fk\d*|idx)$ |