All dbLinter rules

• 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-1060 Avoid storing ROWIDs or UROWIDs in database tables.

  Reliability
• 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-1110 Avoid connect users that own database objects.

  Security
• G-1120 Avoid granting system privileges to connect users.

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

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

  Maintainability
• G-1150 Always limit privileges of schema owners according to principle of least privileges.

  Security
• G-1210 Never create a table without a primary key.

  Reliability
• G-1220 Avoid composite primary keys.

  Maintainability
• G-1230 Avoid tables without relationships.

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

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

  Reliability
• 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-1310 Never keep database objects in an invalid state.

  Reliability
• G-1910 Avoid using the NOSONAR marker.

  Maintainability
• G-1920 Avoid syntax errors.

  Maintainability
• G-1930 Avoid long parsing times.

  Maintainability
• G-1940 Avoid long checking times.

  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-2140 Never initialize variables with NULL.

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

  Maintainability
• G-2150 Avoid comparisons with NULL value, consider using IS [NOT] NULL.

  Reliability
• G-2160 Avoid initializing variables using functions in the declaration section.

  Reliability
• 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-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-2320 Never use VARCHAR data type.

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

  Maintainability
• G-2340 Always define your VARCHAR2 variables using CHAR SEMANTIC (if not defined anchored).

  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-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-3140 Try to use anchored records as targets for your cursors.

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

  Reliability
• G-3150 Try to use identity columns for surrogate keys.

  Reliability
• G-3160 Avoid visible virtual columns.

  Reliability
• G-3170 Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.

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

  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-3185 Never use ROWNUM at the same query level as ORDER BY.

  Reliability
• G-3190 Avoid using NATURAL JOIN.

  Reliability
• G-3192 Avoid joining tables with the USING clause.

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

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

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

  Maintainability
• G-3330 Avoid autonomous transactions.

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

  Maintainability
• 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-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-4230 Always use a COALESCE instead of a NVL command, if parameter 2 of the NVL function is a function call or a SELECT statement.

  Reliability
• 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-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-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-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-5030 Never assign predefined exception names to user defined exceptions.

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

  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-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-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-7127 Always use the FORCE option when creating views.

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

  Reliability
• 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-7180 Try to keep the complexity of functions, procedures and triggers simple.

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

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

  Maintainability
• G-7230 Avoid declaring global variables public.

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

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

  Reliability
• G-7510 Always prefix Oracle supplied packages with owner schema name.

  Security
• G-7515 Always prefix Oracle supplied object types with owner schema name.

  Security
• 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-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-7810 Never use SQL inside PL/SQL to read sequence numbers (or SYSDATE).

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

  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-8310 Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.

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

  Reliability
• 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-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 types.

  Maintainability
• 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

189 total