Query goal: | Write correct constraints. Usually the constraint expression should refer to at least one column. A domain constraint expression should refer to the stub VALUE. For instance, the constraint CHECK(1=0) that is associated with a table T would prevent adding any rows to T. The value of the Boolean expression of this constraint is always FALSE. |
Notes about the query: | The query considers check constraints of all the domains, regardless of whether the domain is used do define a column in a base table or not. |
Query type: | Problem detection (Each row in the result could represent a flaw in the design) |
Query reliability: | High (Few or no false-positive results) |
Query license: | MIT License |
Data source: | INFORMATION_SCHEMA+system catalog |
SQL query: | Click on query to copy it
select n.nspname as schema, c.relname || '.' || o.conname as name, substring(pg_get_constraintdef(o.oid),7) as expression, 'TABLE CHECK' AS type from pg_constraint o inner join pg_class c on c.oid = o.conrelid inner join pg_namespace n on n.oid=c.relnamespace where o.contype ='c' and n.nspname not in (select schema_name from information_schema.schemata where schema_name<>'public' and schema_owner='postgres' and schema_name is not null) and conkey is null union select n.nspname as schema, t.typname || '.' || o.conname as name, substring(pg_get_constraintdef(o.oid),7) as expression, 'DOMAIN CHECK' AS type from pg_constraint o inner join pg_type t on t.oid = o.contypid inner join pg_namespace n on n.oid=t.typnamespace where o.contype ='c' and n.nspname not in (select schema_name from information_schema.schemata where schema_name<>'public' and schema_owner='postgres' and schema_name is not null) and substring(pg_get_constraintdef(o.oid),7) !~ '([(]VALUE|VALUE[)])' order by type, schema, name; |
Collection name | Collection description |
---|---|
Find problems automatically | Queries, that results point to problems in the database. Each query in the collection produces an initial assessment. However, a human reviewer has the final say as to whether there is a problem or not . |
Category name | Category description |
---|---|
CHECK constraints | Queries of this category provide information about CHECK constraints. |
Fatal problems | Queries of this category provide information about problems that render a part of a database unusable. |
Stubs | Queries of this catergory provide information about stubs (piece of code used to stand in for some other programming functionality). |
Validity and completeness | Queries of this category provide information about whether database design represents the world (domain) correctly (validity) and whether database design captures all the information about the world (domain) that is correct and relevant (completeness). |