Rules with quality area Maintainability

Maintainability refers to the ease with which you can repair, improve and understand software code.

• G-1010 Try to label your sub blocks.

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

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

  Maintainability
• G-1040 Avoid dead code.

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

  Maintainability
• G-1070 Avoid nesting comment blocks.

  Maintainability
• G-1080 Avoid using the same expression on both sides of a relational comparison operator or a logical operator.

  Maintainability
• G-1130 Avoid granting table access to API roles.

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

  Maintainability
• G-1220 Avoid composite primary keys.

  Maintainability
• G-1230 Avoid tables without relationships.

  Maintainability
• G-1260 Try to define a comment for each table.

  Maintainability
• G-1270 Try to define a comment for each column.

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

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

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

  Maintainability
• G-2140 Never initialize variables with NULL.

  Maintainability
• G-2145 Never self-assign a variable.

  Maintainability
• G-2170 Never overload variables.

  Maintainability
• G-2180 Never use quoted identifiers.

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

  Maintainability
• G-2320 Never use VARCHAR data type.

  Maintainability
• G-2330 Never use zero-length strings to substitute NULL.

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

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

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

  Maintainability
• G-3115 Avoid self-assigning a column.

  Maintainability
• 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-3183 Always specify column aliases instead of expressions in GROUP BY clauses.

  Maintainability
• G-3195 Always use wildcards in a LIKE clause.

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

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

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

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

  Maintainability
• G-4250 Avoid using identical conditions in different branches of the same IF or CASE statement.

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

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

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

  Maintainability
• G-4320 Always label your loops.

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

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

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

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

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

  Maintainability
• G-4385 Never use a cursor for loop to check whether a cursor returns data.

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

  Maintainability
• G-5020 Never handle unnamed exceptions using the error number.

  Maintainability
• 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-5080 Always use FORMAT_ERROR_BACKTRACE when using FORMAT_ERROR_STACK or SQLERRM.

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

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

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

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

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

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

  Maintainability
• G-7150 Try to remove unused parameters.

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

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

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

  Maintainability
• G-7330 Always assign values to OUT parameters.

  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-7450 Never return a NULL value from a BOOLEAN function.

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

  Maintainability
• G-7710 Avoid cascading triggers.

  Maintainability
• G-7720 Never use multiple UPDATE OF in trigger event clause.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  Maintainability

109 total