| 201 |
Perhaps incorrect column name (based on default values) |
Find columns of base tables that have the default value CURRENT_USER or SESSION_USER but the name of the column does not refer to the fact that it contains usernames. |
Problem detection |
INFORMATION_SCHEMA only |
2024-01-01 12:14 |
MIT License |
View |
| 202 |
Simple check constraints with multiple tasks |
Find simple check constraints, i.e., check constraints that cover one column that seem to have multiple tasks. The corresponding code smell in case of cleaning code is "G30: Functions Should Do One Thing". (Robert C. Martin, Clean Code) |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2024-01-01 11:42 |
MIT License |
View |
| 203 |
All table CHECK constraints that cover at leat one column |
Find all CHECK constraints (except NOT NULL) that are associated with a base table or a foreign table column. It is useful to enforce as many constraints at database level as possible. In this way one improves data quality as well as gives extra information to the database users (including the DBMS engines, development environments, and applications). |
General |
INFORMATION_SCHEMA only |
2024-01-01 11:27 |
MIT License |
View |
| 204 |
Multiple tables share the same state classifier |
Find cases where multiple tables share the same state classifier. For each main entity type one should create a separate state classifier table. Even if the classifier values are the same in case of two entity types for now these may become different in the future. Having a shared state classifier table usually means very simplistic state machines (states active and inactive) that could point to the gaps in analysis. |
Problem detection |
system catalog base tables only |
2023-12-30 15:51 |
MIT License |
View |
| 205 |
Perhaps last update time trigger is missing |
Find base tables that have a column for last update time but the table does not have associated before update row level trigger for changing the last update time. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-30 15:22 |
MIT License |
View |
| 206 |
Perhaps an overcomplicated constraint expression that compares the result of a Boolean expression with a Boolean value |
Find table and domain CHECK constraints that compare the result of a Boolean expression with a Boolean value. If you can choose between two logically equivalent Boolean expressions choose the more simple expression. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-30 11:57 |
MIT License |
View |
| 207 |
Inconsistent use of session_user and current_user functions |
Find as to whether both functions session_user and current_user are used in the database. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-30 11:37 |
MIT License |
View |
| 208 |
Perhaps incorrect default vale |
Find columns of base tables that have default value CURRENT_USER. |
Problem detection |
INFORMATION_SCHEMA only |
2023-12-30 11:32 |
MIT License |
View |
| 209 |
Incorrect data type (based on default values) |
Find columns of base tables that have the default value CURRENT_USER or SESSION_USER but the data type is CHAR or TEXT. |
Problem detection |
INFORMATION_SCHEMA only |
2023-12-30 11:06 |
MIT License |
View |
| 210 |
Incorrect field size (based on default values) |
Find columns of base tables that have the default value CURRENT_USER or SESSION_USER but the field size is not 63 (default maximum identifier length in PostgreSQL). |
Problem detection |
INFORMATION_SCHEMA only |
2023-12-30 11:05 |
MIT License |
View |
| 211 |
Do not format comma-separated lists (based on default values) |
Find, based on default values, cases where a multi-valued attribute in a conceptual data model is implemented as a textual column of a base table or a foreign table. Expected values in the column are strings that contain attribute values, separated by commas or other separation characters. |
Problem detection |
INFORMATION_SCHEMA only |
2023-12-30 10:59 |
MIT License |
View |
| 212 |
Perhaps the type of a base table column/domain should be numeric (based on default values) |
Specify for each column/domain a right data type that takes into account expected values in the column/domain. Find base table columns and domains that have a textual type but the default value that represents a number (for instance, '100', '2', or '0.22'). Exclude columns about formats. |
Problem detection |
INFORMATION_SCHEMA only |
2023-12-30 10:59 |
MIT License |
View |
| 213 |
Do not leave out the referential constraints (based on column names) (2) |
Try to find missing foreign key constraints. Find columns of base tables that are not a part of any primary key, unique, and foreign key constraint, but have a name that reffers to the possibility that these are used to record references to a user. Exclude columns that have the default value CURRENT_USER or SESSION_USER. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-30 10:29 |
MIT License |
View |
| 214 |
Perhaps unnecessary DECLARE section in a PL/pgSQL routine |
Find PL/pgSQL routines that perhaps unnecessarily contain DECLARE section. More specifically, find routines with the DECLARE section where the only task seems to be raising an exception. The query excludes the cases where the error message is constructed dynamically, i.e., in this case using a variable maybe justifiable. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-30 10:19 |
MIT License |
View |
| 215 |
CHECK constraints on columns with personal names |
Find CHECK constraints on base table or foreign table columns that contain data about personal names. Make sure that the constraints do not restrict registration of legal names. |
General |
INFORMATION_SCHEMA only |
2023-12-25 12:51 |
MIT License |
View |
| 216 |
CHECK constraints with the cardinality bigger than one that involve the same set of columns |
CHECK constraints with the cardinality bigger than one that involve the same set of columns. Make sure that there is no duplication. |
General |
system catalog base tables only |
2023-12-25 12:39 |
MIT License |
View |
| 217 |
CHECK constraints with the cardinality bigger than one |
Find multicolumn CHECK constraints. Such constraints must be associated directly with a base table, i.e., these cannot be associated with a domain. Enforce as much data integrity as possible at the database level and prefer declarative constraints to a trigger. |
General |
system catalog base tables only |
2023-12-25 12:38 |
MIT License |
View |
| 218 |
CHECK constraints on columns with temporal data |
If your table contains columns with temporal data, then it will be appropriate to restrict the range of possible values in these columns because some of the values that belong to the type might not be appropriate (for instance, imagine a client who was born in 1100-12-03 or a contract that was registered in 3890-12-12- 12:45). If your table contains multiple columns with temporal data that denote events, then the rule about the order of the events must be enforced, if possible. |
General |
INFORMATION_SCHEMA only |
2023-12-25 12:37 |
MIT License |
View |
| 219 |
Derived table presents the same data in the same way as a single base table |
Find derived tables (views and materialized views) that present data from one base table without adding columns, renaming columns, changing the order of columns, removing columns, or restricting rows. Perhaps something is missing from the subquery of the derived table. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-25 12:15 |
MIT License |
View |
| 220 |
A large number of triggers |
Show user-defined triggers if there are more than 9 different trigger routine bodies, i.e., different triggers on different tables that do the same thing count as one trigger. |
General |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-25 11:23 |
MIT License |
View |