PostgreSQL rules

16 of the 228 dbLinter rules apply to PostgreSQL and PL/pgSQL code. New rules are listed on What's new.

• G-0010 New Always format database code consistently.

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

  Blocker Maintainability
• G-1910 Avoid using the NOSONAR marker.

  Info Maintainability
• G-1920 Avoid syntax errors.

  Blocker Maintainability
• G-1930 Avoid long parsing times.

  Info Maintainability
• G-1940 Avoid long checking times.

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

  Blocker Reliability
• G-3110 Always specify the target columns when coding an insert statement.

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

  Blocker Maintainability
• G-3120 Always use table aliases when your SQL statement involves more than one source.

  Blocker Maintainability
• G-3130 Try to use ANSI SQL-92 join syntax.

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

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

  Major Reliability
• G-3190 Avoid using NATURAL JOIN.

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

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

  Blocker Maintainability

16 total