Rules with severity level Minor

Will have a low impact on the maintenance cost. No impact on the runtime behavior.

• A-0730Always give an alias to pages.

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

  Maintainability
• G-1010Try to label your sub blocks.

  Maintainability
• G-1020Always have a matching loop or block label.

  Maintainability
• G-1030Avoid defining variables that are not used.

  Maintainability
• G-1040Avoid dead code.

  Maintainability
• G-1050Avoid using literals in your code.

  Maintainability
• G-1070Avoid nesting comment blocks.

  Maintainability
• A-1130Always follow naming conventions for page items.

  Maintainability
• G-1140Avoid granting object privileges directly to connect users.

  Maintainability
• G-1280Try to use domains instead of raw datatypes for table columns.

  Maintainability
• G-2120Try to have a single location to define your types.

  Maintainability
• G-2130Try to use subtypes for constructs used often in your code.

  Maintainability
• G-2140Never initialize variables with NULL.

  Maintainability
• G-2410Try to use boolean data type for values with dual meaning.

  Maintainability
• G-2610Never use self-defined weak ref cursor types.

  Maintainability
• G-3183Always specify column aliases instead of expressions in GROUP BY clauses.

  Maintainability
• G-4110Always use %NOTFOUND instead of NOT %FOUND to check whether a cursor returned data.

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

  Maintainability
• G-4260Avoid inverting boolean conditions with NOT.

  Maintainability
• G-4270Avoid comparing boolean values to boolean literals.

  Maintainability
• G-4320Always label your loops.

  Maintainability
• G-4375Always use EXIT WHEN instead of an IF statement to exit from a loop.

  Maintainability
• G-4380Try to label your EXIT WHEN statements.

  Maintainability
• G-4395Avoid hard-coded upper or lower bound values with FOR loops.

  Maintainability
• G-6020Try to use output bind arguments in the RETURNING INTO clause of dynamic DML statements rather than the USING clause.

  Maintainability
• G-7120Always add the name of the program unit to its end keyword.

  Maintainability
• G-7210Try to keep your packages small. Include only few procedures and functions that are used in the same context.

  Reliability
• G-7220Always use forward declaration for private functions and procedures.

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

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

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

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

  Maintainability
• G-8310Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.

  Maintainability
• G-9101Always follow naming conventions for global variables.

  Maintainability
• G-9102Always follow naming conventions for local variables.

  Maintainability
• G-9103Always follow naming conventions for cursor variables.

  Maintainability
• G-9104Always follow naming conventions for record variables.

  Maintainability
• G-9105Always follow naming conventions for collection variables (arrays/tables).

  Maintainability
• G-9106Always follow naming conventions for object variables.

  Maintainability
• G-9107Always follow naming conventions for cursor parameters.

  Maintainability
• G-9108Always follow naming conventions for IN parameters of functions and procedures.

  Maintainability
• G-9109Always follow naming conventions for OUT parameters of functions and procedures.

  Maintainability
• G-9110Always follow naming conventions for IN/OUT parameters of functions and procedures.

  Maintainability
• G-9111Always follow naming conventions for record type definitions.

  Maintainability
• G-9112Always follow naming conventions for collection type definitions (arrays/tables).

  Maintainability
• G-9113Always follow naming conventions for exceptions.

  Maintainability
• G-9114Always follow naming conventions for constants.

  Maintainability
• G-9115Always follow naming conventions for subtypes.

  Maintainability
• G-9116Always follow naming conventions for record fields.

  Maintainability
• G-9201Always follow naming conventions for tables.

  Maintainability
• G-9202Always follow naming conventions for table/view columns.

  Maintainability
• 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
• G-9208Always follow naming conventions for assertions.

  Maintainability
• G-9209Always follow naming conventions for global temporary tables.

  Maintainability
• G-9210Always follow naming conventions for views.

  Maintainability
• G-9211Always follow naming conventions for sequences.

  Maintainability
• G-9212Always follow naming conventions for synonyms.

  Maintainability
• G-9213Always follow naming conventions for triggers.

  Maintainability
• G-9214Always follow naming conventions for PL/SQL packages.

  Maintainability
• G-9215Always follow naming conventions for functions.

  Maintainability
• G-9216Always follow naming conventions for procedures.

  Maintainability
• G-9217Always follow naming conventions for object types.

  Maintainability
• G-9218Always follow naming conventions for object type attributes.

  Maintainability
• G-9219Always follow naming conventions for collection types.

  Maintainability

69 total