rules repository

G-9215 – Always follow naming conventions for functions.

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 in general. Nevertheless, it is not sensible to call a function `get_...` as a function always gets something. The name of the function should answer the question “What is the outcome of the function?” Optionally prefixed by a project abbreviation. **Example**: `employee_by_id` If more than one function provides the same outcome, you have to be more specific with the name.

Tags: Naming SQL.

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

No rule selected