G-9113

🆓

Warning

Always follow naming conventions for exceptions.

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
   some_name exception;
begin
   null;
end;
/

Issues

Line	Column	Message
2	4	Exception some_name does not match '^e_[a-z0-9$#_]+$'.

Compliant Solution - ★★★★★

declare
   e_some_name exception;
begin
   null;
end;
/

Parameters

Use parameters to customize the rule to your needs.

Parameter	Description	Default Value
ExceptionPattern	Case-insensitive regular expression pattern for PL/SQL exceptions.	^e_[a-z0-9$#_]+$

References

same as plsql:NamingExceptionsCheck
same as Trivadis Naming Conventions for PL/SQL - Exception