G-9202
🆓Warning
Always follow naming conventions for table/view columns.
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
Singular name of what is stored in the column (unless the column data type is a collection, in this case you use plural names).
Add a comment to the database dictionary for every column. See also G-1270.
Example
Non-Compliant Example
create table departements ( numéro_de_département number -- ... );
Issues
| Line | Column | Message |
|---|---|---|
| 2 | 4 | column numéro_de_département does not match '^[a-z0-9$#_]+'. |
Explanation
We do not want accented letters in column names.
Compliant Solution - ★★★★★
create table departements ( numero_de_departement number -- ... );
Explanation
All accented letters are replaced with plain Latin letters.
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| ColumnPattern | Case-insensitive regular expression pattern for SQL table/view column names. | ^[a-z][a-z0-9$#_]*$ |