G-9214
🆓Warning
Always follow naming conventions for PL/SQL packages.
Reason
SQL identifiers share the same namespace as PL/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.
Recommendations
Name is built from the content that is contained within the package.
Optionally prefixed by a project abbreviation.
Examples
employees_api- API for the employee tablelogging_up- Utilities including logging support
Example
Non-Compliant Example
create or replace package département_api is -- ... end; /
Issues
| Line | Column | Message |
|---|---|---|
| 1 | 27 | package département_api does not match '^[a-z][a-z0-9$#_]*$'. |
Explanation
We do not want accented letters in package names.
Compliant Solution - ★★★★★
create or replace package departement_api is -- ... end; /
Explanation
All accented letters are replaced with plain Latin letters.
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| PackagePattern | Case-insensitive regular expression pattern for PL/SQL packages. | ^[a-z][a-z0-9$#_]*$ |
References
- same as plsql:PlSql.PackageNaming