Rules with fixing time Other

Local change and changes in other modules. For example, replace the use of ROWID with primary keys in tables and code.

• G-1060Avoid storing ROWIDs or UROWIDs in database tables.

  Reliability
• G-1110Avoid connect users that own database objects.

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

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

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

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

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

  Reliability
• 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-1260Try to define a comment for each table.

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

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

  Maintainability
• G-1310Never keep database objects in an invalid state.

  Reliability
• G-1910Avoid using the NOSONAR marker.

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

  Reliability
• G-3160Avoid visible virtual columns.

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

  Reliability
• G-3330Avoid autonomous transactions.

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

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

42 total