G-9211
🆓Warning
Always follow naming conventions for sequences.
Reason
SQL identifiers share the same namespace as PL/SQL identifiers. 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
Name is built from the table name (or its abbreviation) the sequence serves as primary key generator and the suffix _seq or the purpose of the sequence followed by a _seq.
Optionally prefixed by a project abbreviation.
Examples
employees_seqorder_number_seq
Example
Non-Compliant Example
create sequence emps;
Issues
| Line | Column | Message |
|---|---|---|
| 1 | 17 | sequence emps does not match '^[a-z][a-z0-9$#_]*_seq$'. |
Compliant Solution - ★★★★★
create sequence emp_seq;
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| SequencePattern | Case-insensitive regular expression pattern for SQL sequences. | ^[a-z][a-z0-9$#_]*_seq$ |