Filter Queries

Found 1053 queries.

  • All the queries about database objects contain a subcondition to exclude from the result information about the system catalog.
  • Although the statements use SQL constructs (common table expressions; NOT in subqueries) that could cause performance problems in case of large datasets it shouldn't be a problem in case of relatively small amount of data, which is in the system catalog of a database.
  • Statistics about the catalog content and project home in GitHub that has additional information.

#581. INFORMATION_SCHEMA is missing

INFORMATION_SCHEMA+system catalog base tables

Make sure that you do not drop INFORMATION_SCHEMA schema. In this case most of the design checking queries will not work. This schema automatically exists in all databases.

Problem detection License: MIT (opens in new tab)

#582. Input parameters that names do not follow the convention to start with _ or p_

INFORMATION_SCHEMA+system catalog base tables

For the sake of making code better understandable follow naming conventions.

Problem detection License: MIT (opens in new tab)

#583. Installed extensions

system catalog base tables only

Try to use as much the possibilities of the DBMS as possible. On the other hand, do not install extensions that are not needed in order not to overcomplicate the database.

General License: MIT (opens in new tab)

#584. Insufficient routine privileges

INFORMATION_SCHEMA+system catalog base tables

You must give rights to use routines to the users/roles that correspond to applications.

Problem detection License: MIT (opens in new tab)

#585. Insufficient view privileges

INFORMATION_SCHEMA+system catalog base tables

You must give privileges to use views to the users/roles that correspond to applications

Problem detection License: MIT (opens in new tab)

#586. Invalid character class

INFORMATION_SCHEMA+system catalog base tables

PostgreSQL regular expressions do not have character classes word and letter.

Problem detection License: MIT (opens in new tab)

#587. Invalid use of the case insensitive search modifier in regular expressions

INFORMATION_SCHEMA+system catalog base tables

Find regular expression patterns that use (?i) modifier in any other place than at the beginning of the pattern or (?-i) in any place of the pattern. Such use of the modifiers is not supported by PostgreSQL.

Problem detection License: MIT (opens in new tab)

#588. Invocation of a system-defined routine without providing any arguments

INFORMATION_SCHEMA+system catalog base tables

Find user-defined routines that contain an invocation of a system-defined function without providing any argument. The query considers all aggregate functions as well as some popular scalar functions.

Problem detection License: MIT (opens in new tab)

#589. Invocation of PL/pgSQL functions from the subqueries of derived tables

INFORMATION_SCHEMA+system catalog base tables

Find derived tables that subqueries invoke a PL/pgSQL function. Avoid context switch that is caused by the invocation of PL/pgSQL functions from the subqueries of derived tables.

Problem detection License: MIT (opens in new tab)

#590. IS DISTINCT FROM should be used instead of <> in WHEN clauses

INFORMATION_SCHEMA only

Use a right predicate in trigger condition in order to ensure that the trigger executes always when it has to but not more often. IS DISTINCT FROM treats NULL as if it was a known value, rather than unknown. It would be relevant if a column that is referenced in the action condition is optional, i.e., permits NULLs.

Problem detection License: MIT (opens in new tab)

#591. IS NOT DISTINCT FROM in derived tables

INFORMATION_SCHEMA+system catalog base tables

Avoid using IS NOT DISTINCT FROM because it makes the query planner to avoid using an index.

Problem detection License: MIT (opens in new tab)

#592. IS NOT DISTINCT FROM in routines

INFORMATION_SCHEMA+system catalog base tables

Avoid using IS NOT DISTINCT FROM because it makes the query planner to avoid using an index.

Problem detection License: MIT (opens in new tab)

#593. IS NULL check is probably not needed

INFORMATION_SCHEMA only

Find CHECK constraints that refer only to mandatory columns but the Boolean expression has IS NULL condition.

Problem detection License: MIT (opens in new tab)

#594. JSON type instead of JSONB type

INFORMATION_SCHEMA only

"In general, most applications should prefer to store JSON data as jsonb, unless there are quite specialized needs, such as legacy assumptions about ordering of object keys." (https://www.postgresql.org/docs/current/datatype-json.html)

Problem detection License: MIT (opens in new tab)

#595. LEAKPROOF routines that are perhaps not leakproof

INFORMATION_SCHEMA+system catalog base tables

You should not give wrong information to the database management system.

Problem detection License: MIT (opens in new tab)

#596. Lifecycle not initiated

INFORMATION_SCHEMA+system catalog base tables

Find non-primary key and non-unique base table foreign key columns that name refers to the possibility that these are used to register references to a state classifier. The column must belong to a foreign key and does not have a default value.

Problem detection License: MIT (opens in new tab)

#597. LIKE instead of =

INFORMATION_SCHEMA+system catalog base tables

Find expressions that use LIKE predicate for precise comparison.

Problem detection License: MIT (opens in new tab)

#598. LIKE with a regular expression pattern

INFORMATION_SCHEMA+system catalog base tables

Find expressions that use LIKE (including ILIKE) predicate with a regular expression patterns. In a LIKE pattern one can use only _ and % metasymbols to construct a pattern.

Problem detection License: MIT (opens in new tab)

#599. LIKE without a pattern with % or _

INFORMATION_SCHEMA+system catalog base tables

Find expressions that use LIKE predicate witout a pattern that contains at least one % or _ sign.

Problem detection License: MIT (opens in new tab)

#600. Logical size of a schema

INFORMATION_SCHEMA+system catalog base tables

The schema size is the sum of the sizes of all tables in the schema.

Sofware measure License: MIT (opens in new tab)
# Name Goal Type Data source Last update (sorted descending) License Actions
581 INFORMATION_SCHEMA is missing Make sure that you do not drop INFORMATION_SCHEMA schema. In this case most of the design checking queries will not work. This schema automatically exists in all databases. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
582 Input parameters that names do not follow the convention to start with _ or p_ For the sake of making code better understandable follow naming conventions. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
583 Installed extensions Try to use as much the possibilities of the DBMS as possible. On the other hand, do not install extensions that are not needed in order not to overcomplicate the database. General system catalog base tables only MIT (opens in new tab) View (opens in new tab)
584 Insufficient routine privileges You must give rights to use routines to the users/roles that correspond to applications. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
585 Insufficient view privileges You must give privileges to use views to the users/roles that correspond to applications Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
586 Invalid character class PostgreSQL regular expressions do not have character classes word and letter. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
587 Invalid use of the case insensitive search modifier in regular expressions Find regular expression patterns that use (?i) modifier in any other place than at the beginning of the pattern or (?-i) in any place of the pattern. Such use of the modifiers is not supported by PostgreSQL. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
588 Invocation of a system-defined routine without providing any arguments Find user-defined routines that contain an invocation of a system-defined function without providing any argument. The query considers all aggregate functions as well as some popular scalar functions. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
589 Invocation of PL/pgSQL functions from the subqueries of derived tables Find derived tables that subqueries invoke a PL/pgSQL function. Avoid context switch that is caused by the invocation of PL/pgSQL functions from the subqueries of derived tables. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
590 IS DISTINCT FROM should be used instead of <> in WHEN clauses Use a right predicate in trigger condition in order to ensure that the trigger executes always when it has to but not more often. IS DISTINCT FROM treats NULL as if it was a known value, rather than unknown. It would be relevant if a column that is referenced in the action condition is optional, i.e., permits NULLs. Problem detection INFORMATION_SCHEMA only MIT (opens in new tab) View (opens in new tab)
591 IS NOT DISTINCT FROM in derived tables Avoid using IS NOT DISTINCT FROM because it makes the query planner to avoid using an index. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
592 IS NOT DISTINCT FROM in routines Avoid using IS NOT DISTINCT FROM because it makes the query planner to avoid using an index. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
593 IS NULL check is probably not needed Find CHECK constraints that refer only to mandatory columns but the Boolean expression has IS NULL condition. Problem detection INFORMATION_SCHEMA only MIT (opens in new tab) View (opens in new tab)
594 JSON type instead of JSONB type "In general, most applications should prefer to store JSON data as jsonb, unless there are quite specialized needs, such as legacy assumptions about ordering of object keys." (https://www.postgresql.org/docs/current/datatype-json.html) Problem detection INFORMATION_SCHEMA only MIT (opens in new tab) View (opens in new tab)
595 LEAKPROOF routines that are perhaps not leakproof You should not give wrong information to the database management system. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
596 Lifecycle not initiated Find non-primary key and non-unique base table foreign key columns that name refers to the possibility that these are used to register references to a state classifier. The column must belong to a foreign key and does not have a default value. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
597 LIKE instead of = Find expressions that use LIKE predicate for precise comparison. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
598 LIKE with a regular expression pattern Find expressions that use LIKE (including ILIKE) predicate with a regular expression patterns. In a LIKE pattern one can use only _ and % metasymbols to construct a pattern. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
599 LIKE without a pattern with % or _ Find expressions that use LIKE predicate witout a pattern that contains at least one % or _ sign. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
600 Logical size of a schema The schema size is the sum of the sizes of all tables in the schema. Sofware measure INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)