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.

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

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

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

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

  Reliability
• G-3190 Avoid using NATURAL JOIN.

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

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

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

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

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

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

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

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

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

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

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

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

  Reliability
• G-7230 Avoid declaring global variables public.

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

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

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

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

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

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

  Maintainability
• G-7710 Avoid cascading triggers.

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

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

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

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

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

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

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

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

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

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

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

  Maintainability

36 total