G-9115
🆓Warning
Always follow naming conventions for subtypes.
Reason
PL/SQL identifiers share the same namespace as 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.
Example
Non-Compliant Example
declare subtype short_text is varchar2(100 char); begin null; end; /
Issues
| Line | Column | Message |
|---|---|---|
| 2 | 12 | Subtype short_text does not match '^[a-z][a-z0-9$#_]*_type$'. |
Compliant Solution - ★★★★★
declare subtype short_text_type is varchar2(100 char); begin null; end; /
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| SubtypePattern | Case-insensitive regular expression pattern for PL/SQL subtypes. | ^[a-z][a-z0-9$#_]*_type$ |
References
- similar to plsql:NamingTypesCheck
The scope of plsql:NamingTypesCheck is all types, not just subtype definitions.