Rules with severity level Major

Will have a medium/potential impact on the maintenance cost. May have an impact on runtime behavior; for example, higher memory consumption.

• G-1220Avoid composite primary keys.

  Maintainability
• G-1230Avoid tables without relationships.

  Maintainability
• G-1240Try to index foreign key columns.

  Reliability
• G-1250Try to define a business key for each table.

  Reliability
• G-2110Try to use anchored declarations for variables, constants and types.

  Reliability
• G-2135Avoid assigning values to local variables that are not used by a subsequent statement.

  Reliability
• G-2170Never overload variables.

  Maintainability
• G-2180Never use quoted identifiers.

  Maintainability
• G-2185Avoid using overly short names for explicitly or implicitly declared identifiers.

  Maintainability
• G-2510Avoid using the LONG and LONG RAW data types.

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

  Maintainability
• G-3140Try to use anchored records as targets for your cursors.

  Reliability
• G-3180Always specify column names instead of positional references in ORDER BY clauses.

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

  Maintainability
• G-4220Try to use CASE rather than DECODE.

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

  Maintainability
• G-4325Never reuse labels in inner scope.

  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-4365Never use unconditional CONTINUE or EXIT in a loop.

  Maintainability
• G-4370Avoid using EXIT to stop loop processing unless you are in a basic loop.

  Maintainability
• G-4390Avoid use of unreferenced FOR loop indexes.

  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-5060Avoid unhandled exceptions.

  Reliability
• G-6010Always use a character variable to execute dynamic SQL.

  Maintainability
• G-7110Try to use named notation when calling program units.

  Maintainability
• G-7125Always use CREATE OR REPLACE instead of CREATE alone.

  Maintainability
• G-7127Always use the FORCE option when creating views.

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

  Reliability
• G-7140Always ensure that locally defined procedures or functions are referenced.

  Maintainability
• G-7150Try to remove unused parameters.

  Maintainability
• G-7160Always explicitly state parameter mode.

  Reliability
• G-7170Avoid using an IN OUT parameter as IN or OUT only.

  Reliability
• G-7230Avoid declaring global variables public.

  Reliability
• G-7250Never use RETURN in package initialization block.

  Reliability
• G-7320Avoid using RETURN statements in a PROCEDURE.

  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-7460Try to define your packaged/standalone function deterministic if appropriate.

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

  Maintainability
• G-7710Avoid cascading triggers.

  Maintainability
• G-9030Try to define a default value on conversion errors.

  Maintainability

43 total