G-9217
🆓Warning
Always follow naming conventions for object types.
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
The name of an object type is built by its content (singular) followed by a _ot suffix.
Optionally prefixed by a project abbreviation.
Example: employee_ot
Example
Non-Compliant Example
create or replace type dept as object ( department_id number -- ... ); /
Issues
| Line | Column | Message |
|---|---|---|
| 1 | 24 | object type dept does not match '^[a-z][a-z0-9$#_]*_ot$'. |
Compliant Solution - ★★★★★
create or replace type dept_ot as object ( department_id number -- ... ); /
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| ObjectTypePattern | Case-insensitive regular expression pattern for SQL object types. | ^[a-z][a-z0-9$#_]*_ot$ |