G-9102
🆓Warning
Always follow naming conventions for local variables.
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.
General local variables that are not based on a record, collection type or object type. However, if the type cannot be determined because it is not defined in the same file, then the patterns for record variables (G-9104), collection variables (G-9105) and object variables (G-9106) are also accepted.
Example
Non-Compliant Example
declare some_name integer; begin null; end; /
Issues
| Line | Column | Message |
|---|---|---|
| 2 | 4 | Local variable some_name does not match '^l_[a-z0-9$#_]+$'. |
Compliant Solution - ★★★★★
declare l_some_name integer; begin null; end; /
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| RecordPattern | Case-insensitive regular expression pattern for PL/SQL local variables of type record. | ^r_[a-z0-9$#_]+$ |
| LocalVariablePattern | Case-insensitive regular expression pattern for PL/SQL common local variables. | ^l_[a-z0-9$#_]+$ |
| CollectionPattern | Case-insensitive regular expression pattern for PL/SQL local variables of type array/table. | ^t_[a-z0-9$#_]+$ |
| ObjectPattern | Case-insensitive regular expression pattern for PL/SQL local variable of SQL object type. | ^o_[a-z0-9$#_]+$ |