Rules with fixing time Local-medium

Local changes in a few locations. For example fix overladed local variable.

• G-1010 Try to label your sub blocks.

  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-2110 Try to use anchored declarations for variables, constants and types.

  Reliability
• 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-2135 Avoid assigning values to local variables that are not used by a subsequent statement.

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

  Maintainability
• G-2170 Never overload variables.

  Maintainability
• G-2190 Avoid using ROWID or UROWID.

  Reliability
• G-2210 Avoid declaring NUMBER variables, constants or subtypes with no precision.

  Reliability
• G-2220 Try to use PLS_INTEGER instead of NUMBER for arithmetic operations with integer values.

  Reliability
• G-2230 Try to use SIMPLE_INTEGER datatype when appropriate.

  Reliability
• G-2310 Avoid using CHAR data type.

  Reliability
• 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-3110 Always specify the target columns when coding an insert statement.

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

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

  Reliability
• G-3182 Always specify column names/aliases instead of positional references in GROUP BY clauses.

  Reliability
• 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-3310 Never commit within a cursor loop.

  Reliability
• G-4120 Avoid using %NOTFOUND directly after the FETCH when working with BULK OPERATIONS and LIMIT clause.

  Reliability
• G-4130 Always close locally opened cursors.

  Reliability
• G-4140 Avoid executing any statements between a SQL operation and the usage of an implicit cursor attribute.

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

  Maintainability
• G-4240 Always use a CASE instead of a NVL2 command if parameter 2 or 3 of NVL2 is either a function call or a SELECT statement.

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

  Maintainability
• G-4320 Always label your loops.

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

  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-4387 Never use a FOR LOOP for a query that should return not more than one row.

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

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

  Maintainability
• G-5010 Try to use a error/logging framework for your application.

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

  Maintainability
• G-5040 Avoid use of WHEN OTHERS clause in an exception section without any other specific handlers.

  Reliability
• G-5060 Avoid unhandled exceptions.

  Reliability
• G-5070 Avoid using Oracle predefined exceptions.

  Reliability
• 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-7140 Always ensure that locally defined procedures or functions are referenced.

  Maintainability
• G-7150 Try to remove unused parameters.

  Maintainability
• G-7160 Always explicitly state parameter mode.

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

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

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

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

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

  Maintainability
• G-7450 Never return a NULL value from a BOOLEAN function.

  Maintainability
• G-7460 Try to define your packaged/standalone function deterministic if appropriate.

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

  Maintainability
• G-7910 Never use DML within a SQL macro.

  Reliability
• 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-8510 Always use dbms_application_info to track program process transiently.

  Reliability
• G-9010 Always use a format model in string to date/time conversion functions.

  Security
• G-9020 Try to use a format model and NLS_NUMERIC_CHARACTERS in string to number conversion functions.

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

  Maintainability
• G-9040 Try using FX in string to date/time conversion format model to avoid fuzzy conversion.

  Reliability
• G-9501 Never use parameter in string expression of dynamic SQL. Use asserted local variable instead.

  Security
• G-9600 Never define more than one comment with hints.

  Reliability
• G-9601 Never use unknown hints.

  Reliability
• G-9602 Always use the alias name instead of the table name.

  Reliability
• G-9603 Never reference an unknown table/alias.

  Reliability
• G-9604 Never use an invalid stats method.

  Reliability
• G-9605 Never use an invalid stats keyword.

  Reliability

77 total