Rules with fixing time Local-high

Local changes in many locations, or where identifying the right action requires some time to think. For example, fixing missing table aliases in columns.

• A-0950Always follow naming conventions for application items.

  Maintainability
• G-1920Avoid syntax errors.

  Maintainability
• G-1930Avoid long parsing times.

  Maintainability
• G-1940Avoid long checking times.

  Maintainability
• G-3120Always use table aliases when your SQL statement involves more than one source.

  Maintainability
• G-3130Try to use ANSI SQL-92 join syntax.

  Maintainability
• G-3145Avoid using SELECT * directly from a table or view.

  Reliability
• G-3185Never use ROWNUM at the same query level as ORDER BY.

  Reliability
• G-3190Avoid using NATURAL JOIN.

  Reliability
• G-3192Avoid joining tables with the USING clause.

  Reliability
• G-3210Always use BULK OPERATIONS (BULK COLLECT, FORALL) whenever you have to execute a DML statement for more than 4 times.

  Reliability
• G-3220Always process saved exceptions from a FORALL statement.

  Reliability
• G-3320Try to move transactions within a non-cursor loop into procedures.

  Maintainability
• G-4210Try to use CASE rather than an IF statement with multiple ELSIF paths.

  Maintainability
• G-4310Never use GOTO statements in your code.

  Maintainability
• G-4330Always use a CURSOR FOR loop to process the complete cursor results unless you are using bulk operations.

  Maintainability
• G-4340Always use a NUMERIC FOR loop to process a dense array.

  Maintainability
• G-4350Always use 1 as lower and COUNT() as upper bound when looping through a dense array.

  Reliability
• G-4360Always use a WHILE loop to process a loose array.

  Reliability
• G-5030Never assign predefined exception names to user defined exceptions.

  Reliability
• G-5050Avoid use of the RAISE_APPLICATION_ERROR built-in procedure with a hard-coded 20nnn error number or hard-coded message.

  Maintainability
• G-7130Always use parameters or pull in definitions rather than referencing external variables in a local program unit.

  Reliability
• G-7180Try to keep the complexity of functions, procedures and triggers simple.

  Maintainability
• G-7230Avoid declaring global variables public.

  Reliability
• G-7310Avoid standalone procedures – put your procedures in packages.

  Maintainability
• G-7410Avoid standalone functions – put your functions in packages.

  Maintainability
• G-7420Always make the RETURN statement the last statement of your function.

  Maintainability
• G-7430Try to use no more than one RETURN statement within a function.

  Maintainability
• G-7440Never use OUT parameters to return values from a function.

  Maintainability
• G-7520Avoid using deprecated units in your own code.

  Maintainability
• G-7710Avoid cascading triggers.

  Maintainability
• G-7730Avoid multiple DML events per trigger.

  Reliability
• G-7740Never handle multiple DML events per trigger if primary key is assigned in trigger.

  Reliability
• G-8110Never use SELECT COUNT(*) if you are only interested in the existence of a row.

  Reliability
• G-8120Never check existence of a row to decide whether to create it or not.

  Reliability
• G-8210Always use synonyms when accessing objects of another application schema.

  Maintainability
• G-8410Always use application locks to ensure a program unit is only running once at a given time.

  Reliability
• G-9203Always follow naming conventions for indexes.

  Maintainability
• G-9204Always follow naming conventions for primary key constraints.

  Maintainability
• G-9205Always follow naming conventions for unique constraints.

  Maintainability
• G-9206Always follow naming conventions for foreign key constraints.

  Maintainability
• G-9207Always follow naming conventions for check constraints.

  Maintainability

42 total