G-9216 – Always follow naming conventions for procedures.

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 a verb followed by a noun. The name of the procedure should answer the question “What is done?” Procedures and functions are often named with underscores between words because some editors write all letters in uppercase in the object tree, so it is difficult to read them. Optionally prefixed by a project abbreviation. **Examples** * `calculate_salary` * `set_hiredate` * `check_order_state`

Tags: Naming SQL.

Quality area: Maintainability. Severity: Minor. Fixing time: Other.