G-7110

🆓

Warning

Try to use named notation when calling program units.

Rule Details

Severity Level: Major
Quality Area: Maintainability
Fixing times: 5 mins
Local-medium
Database Support: OracleDB (v7.3.4 +)

Reason

Named notation makes sure that changes to the signature of the called program unit do not affect your call.

This is not needed for standard functions like (to_char, to_date, nvl, round, etc.) but should be followed for any other stored object having more than one parameter.

Example

Non-Compliant Example

declare
   r_employee employees%rowtype;
   co_id      constant employees.employee_id%type := 107;
begin
   employee_api.employee_by_id(r_employee,co_id);
end;
/

Issues

Line	Column	Message
5	32	Use named notation.
5	43	Use named notation.

Compliant Solution - ★★★★★

declare
   r_employee employees%rowtype;
   co_id      constant employees.employee_id%type := 107;
begin
   employee_api.employee_by_id(
      out_row        => r_employee
     ,in_employee_id => co_id
   );
end;
/

Parameters

Use parameters to customize the rule to your needs.

Parameter	Description	Default Value
OracleMaintainedSchemas	Comma-separated list of Oracle maintained schemas with public synonyms in Oracle Database 23ai Version 23.7.0.25.02. Object prefixed with these owners are accepted.	appqossys, audsys, ctxsys, dvsys, flows_files, gsmadmin_internal, lbacsys, mdsys, outln, sys, system, wmsys, xdb
SchemaNames	Comma-separated list of database schemas owning the database objects of an application.	dbl_owner

References

same as Trivadis G-7110