rules repository

G-9112

🆓
Warning

Always follow naming conventions for collection type definitions (arrays/tables).

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 t_varray is varray(10) of string;
   type nested_table_type is table of string;
   type x_assoc_array_y is table of string index by pls_integer;
begin
   null;
end;
/
Issues
LineColumnMessage
29Collection type definition t_varray does not match '^t_[a-z0-9$#_]+_type$'.
39Collection type definition nested_table_type does not match '^t_[a-z0-9$#_]+_type$'.
49Collection type definition x_assoc_array_y does not match '^t_[a-z0-9$#_]+_type$'.

Compliant Solution - ★★★★★

declare
   type t_varray_type is varray(10) of string;
   type t_nested_table_type is table of string;
   type t_assoc_array_type is table of string index by pls_integer;
begin
   null;
end;
/

Parameters

Use parameters to customize the rule to your needs.

ParameterDescriptionDefault Value
PlsqlCollectionTypePatternCase-insensitive regular expression pattern for PL/SQL collection type definitions.^t_[a-z0-9$#_]+_type$

References

← Previous
G-9111
Always follow naming conventions for record type definitions.
Next →
G-9113
Always follow naming conventions for exceptions.