rules repository

G-9116

🆓
Warning

Always follow naming conventions for record fields.

Naming PL/SQL

Rule Details

Severity Level
Minor
Quality Area
Maintainability
Fixing times
60 mins
Other
Database Support
OracleDB (v7.3.4 +)

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
   type r_dept_type is
      record(
         numéro_de_département number,
         nom                   varchar2(30 char)
      );
begin
   null;
end;
/
Issues
LineColumnMessage
410field numéro_de_département does not match '^[a-z0-9$#_]+'.

Explanation

We do not want accented letters in field names.

Compliant Solution - ★★★★★

declare
   type r_dept_type is
      record(
         numero_de_departement number,
         nom                   varchar2(30 char)
      );
begin
   null;
end;
/

Explanation

All accented letters are replaced with plain Latin letters.

Parameters

Use parameters to customize the rule to your needs.

ParameterDescriptionDefault Value
FieldPatternCase-insensitive regular expression pattern for PL/SQL record fields.^[a-z0-9$#_]+$

References

← Previous
G-9115
Always follow naming conventions for subtypes.
Next →
G-9201
Always follow naming conventions for tables.