| 221 |
Base table column of surrogate key values does not have an integer data type (based on column names) |
Find base table columns that belong to a primary key, unique, or foreign key constraint and that name refers to the possibility that these are used to hold surrogate key values. Find the columns where the data type of the column is not an integer type or uuid. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2025-11-07 10:11 |
MIT License |
View |
| 222 |
Base table columns for recording geographic coordinates (based on column names) |
Find base table columns that are according to the name meant for recording coordinates. |
General |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 223 |
Base table columns for recording geographic coordinates that do not have a suitable type (based on column names) |
Find base table columns that are according to the name meant for recording geographic coordinate but do not have a suitable type (numeric or point). |
Problem detection |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 224 |
Base table columns for storing username, password, and salt |
Find base table columns that name refers to the possibility that these are used to register usernames, passwords, and salt. Password should not be open text. It should be a hash value that has been hashed by using salt. |
General |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 225 |
Base table columns permitting e-mail addresses without @ sign |
Find non-foreign key base table columns that name refers to the possibility that these are used to register e-mail addresses. Find the columns that do not have any simple CHECK constraint that contains @ sign. A simple check constraint covers a single column. In this case registration of e-mail addresses without @ is most probably not prohibited. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2025-11-07 10:11 |
MIT License |
View |
| 226 |
Base table columns permitting negative prices/quantity |
Find non-foreign key base table columns that name refers to the possibility that these are used to register prices/quantities. Find the columns that do not have any simple CHECK constraints, i.e., a constraint that covers only this column. In this case registration of negative price/quantity is most probably not prohibited. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2025-11-07 10:11 |
MIT License |
View |
| 227 |
Base table columns permitting temporal values that may be outside the range of logical values |
Find base tables columns with temporal types (date and timestamp) that do not belong to a foreign key and that do not have any associated simple CHECK constraints, i.e., constraint that involves only one column. For instance, in the column registration_time that does not have any associated CHECK constraints could be values '1200-01-01 00:00' or '5900-12-31 00:00'. Rows with these values most probably represent wrong propositions and the system should restrict registration of such data. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2025-11-07 10:11 |
MIT License |
View |
| 228 |
Base table columns permitting URLs without a protocol |
Find non-foreign key base table columns that name refers to the possibility that these are used to register URLs. Find the columns that do not have any simple CHECK constraint that references to a protocol. A simple check constraint covers a single column. In this case registration of URLs without a protocol is most probably not prohibited. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2025-11-07 10:11 |
MIT License |
View |
| 229 |
Base table columns where TOASTing is possible |
Find all base table columns in case of which the system can use TOAST technique. |
General |
system catalog base tables only |
2025-11-07 10:11 |
MIT License |
View |
| 230 |
Base table columns where TOAST-ing strategy has been changed |
Find base table columns in case of which the system can use TOAST technique (due to the data type of the column) and where the toasting strategy has been changed so that it is different than the default strategy determined by the type. Make sure that the new strategy is optimal. |
General |
system catalog base tables only |
2025-11-07 10:11 |
MIT License |
View |
| 231 |
Base table columns where TOAST-ing strategy has been changed to plain |
Find base table columns in case of which the system can use TOAST technique (due to the data type of the column) and where the toasting strategy has been changed to plain. It means that potentially, if a value in the column is large enough, it is not possible to save the row. |
Problem detection |
system catalog base tables only |
2025-11-07 10:11 |
MIT License |
View |
| 232 |
Base table columns with a composite type |
Find base table columns with a composite type. Think through as to whether a column with a composite type could be replaced with a separate table. |
General |
system catalog base tables only |
2025-11-07 10:11 |
MIT License |
View |
| 233 |
Base table columns with an array type |
Find base table columns with an array type. Think through as to whether a column with an array type could be replaced with a separate table. |
General |
INFORMATION_SCHEMA+system catalog base tables |
2025-11-07 10:11 |
MIT License |
View |
| 234 |
Base table columns with CHAR(n) or VARCHAR(n) type |
Find base table columns with CHAR(n) or VARCHAR(n) type and make sure that n is not too big or too small. Also make sure that you do not use CHAR(n) in case of columns that have to keep variable length strings. "Values of type character are physically padded with spaces to the specified width n, and are stored and displayed that way" (https://www.postgresql.org/docs/current/datatype-character.html) |
General |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 235 |
Base table columns with CITEXT type |
Find base table columns with CITEXT type and make sure that case insensitivity is really needed in case of this column. |
General |
system catalog base tables only |
2025-11-07 10:11 |
MIT License |
View |
| 236 |
Base table columns with DECIMAL (p, s) or NUMERIC (p, s) type |
Find base table columns with DECIMAL (p, s) or NUMERIC (p, s) type and make sure that precision p and scale s are not too big or too small. |
General |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 237 |
Base table columns with one of the following types: BIGINT, INTEGER, TEXT, or VARCHAR without max character length |
Each column should have the most appropriate data type. Developers sometimes misuse BIGINT, INTEGER, TEXT or VARCHAR type in places where a type that permits smaller values would be more appropriate and semantically descriptive. |
General |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 238 |
Base table columns with SMALLINT or BOOLEAN type |
Each column should have the most appropriate data type. Developers sometimes forget to use SMALLINT type even if it is logically the best choice. Developers also sometimes forget to use BOOLEAN type and instead invent something. |
General |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 239 |
Base table columns with the same name and type have different field sizes |
Find base table columns that have the same name and type but different field size. |
Problem detection |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |
| 240 |
Base table columns with the type VARCHAR(1) |
The choice of data types should reveal as much as possible about the nature of the data in the column. The type of these columns could be CHAR(1) and they should have a constraint that a value in the column cannot be an empty string. |
Problem detection |
INFORMATION_SCHEMA only |
2025-11-07 10:11 |
MIT License |
View |