| 261 |
Do not always depend on one's parent - column names are ot sufficiently different |
Find where a hierarchical structure is implemented in a base table by adding a foreign key that refers to a candidate key of the same table. Find only cases where the candidate key and foreign key column names are very similar (Levenshtein distance shorter than four). |
Problem detection |
system catalog base tables only |
2022-11-26 17:19 |
MIT License |
View |
| 262 |
Do not always depend on one's parent (INFORMATION_SCHEMA) |
Find where a hierarchical structure is implemented in a base table by having a foreign key that refers to a candidate key of the same table. This design is called adjacency list. |
General |
INFORMATION_SCHEMA only |
2021-03-07 10:57 |
MIT License |
View |
| 263 |
Do not assume you must use files |
Find cases where you store images and other media as files outside the database and store in the database only paths to the files. |
Problem detection |
INFORMATION_SCHEMA only |
2021-03-27 16:55 |
MIT License |
View |
| 264 |
Do not assume you must use files (based on user data) |
Find cases where you store images and other media as files outside the database and store in the database only paths to the files. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-03-10 12:58 |
MIT License |
View |
| 265 |
Do not clone columns |
"Split a base table column into multiple columns based on the values in some other column. Each such newly created column has the name, a part of which is a data value from the original tables."(Bill Karwin) Find base tables that have more than one columns with the same type and field size and the difference between the columns are the year or month number at the end of the column name (two or four numbers, preceded by an underscore). |
Problem detection |
INFORMATION_SCHEMA only |
2022-11-28 15:15 |
MIT License |
View |
| 266 |
Do not clone tables |
Find cases where a base table has been split horizontally into multiple smaller base tables based on the distinct values in one of the columns of the original table. Each such newly created table has the name, a part of which is a data value from the original tables. Find base tables that have the same columns (column name, column order, data type) and the difference between the tables are the numbers in the table names (table1, table2, etc.). |
Problem detection |
INFORMATION_SCHEMA only |
2021-03-18 14:43 |
MIT License |
View |
| 267 |
Do not create multiple columns for the same attribute |
Find base tables that implement recording multivalued attribute values with the help of repeating group of columns. Find base tables that have more than one columns with the same type and field size and the difference between the columns are the numbers in the column names (column1, column2, etc.). |
Problem detection |
INFORMATION_SCHEMA only |
2021-03-18 15:57 |
MIT License |
View |
| 268 |
Do not create user-defined routines that have the same name as some installed extension routine |
Avoid creating user-defined routines that have the same name as some extension routine because it may cause confusion. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-10-25 16:14 |
MIT License |
View |
| 269 |
Do not format comma-separated lists (based on column names) |
Find, based on column names, 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 |
2021-03-10 12:57 |
MIT License |
View |
| 270 |
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 |
| 271 |
Do not format comma-separated lists (based on user data) |
Find, based on the data that users have recoreded in a database, cases where a multi-valued attribute in a conceptual data model is implemented as a textual column of a base table. Expected values in the column are strings that contain attribute values, separated by commas or other separation characters. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-03-12 15:02 |
MIT License |
View |
| 272 |
Do not leave out referential constraints (based on composite keys) |
Try to find missing foreign key constraints. Find columns of base tables that are not covered by any foreign key constraint but belong to a composite key, do not have an associated sequence generator, and have a name that refers to the possibility that these are used to record some kind of codes or id's. Moreover, there must be at least one other base table that has a column with the same name. Such strategy would find missing constraints in tables that implement many-to-many relationship types but which that are not complete "islands" in terms of missing foreign key constraints. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-10-31 19:21 |
MIT License |
View |
| 273 |
Do not leave out the referential constraints (based on adjacency list design) |
Try to find missing foreign key constraints. Find non-key and non-foreign key columns of base tables that do not have an associated sequence generator, and that name refers to the possibility that the column holds parent identifiers. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-03-18 11:13 |
MIT License |
View |
| 274 |
Do not leave out the referential constraints (based on classifiers) |
Find non-key and non-foreign columns of base tables with a textual column and small field size in case of which there is a table with the name that is similar to the column name. Perhaps the table is a classifier table and the column should have a foreign key constraint referencing to the table. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-03-18 11:14 |
MIT License |
View |
| 275 |
Do not leave out the referential constraints (based on column names) |
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, do not have an associated sequence generator, but have a name that reffers to the possibility that these are used to record some kind of codes or id's. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-11-26 16:35 |
MIT License |
View |
| 276 |
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 |
| 277 |
Do not leave out the referential constraints (islands) |
Try to find missing foreign key constraints. Find base tables that do not participate in any referential constraint (as the referenced table or as the referencing table). These tables are like "islands" in the database schema. |
Problem detection |
system catalog base tables only |
2021-03-10 12:20 |
MIT License |
View |
| 278 |
Do not leave out the referential constraints (pairs of tables) |
Try to find missing foreign key constraints. Find pairs of base table columns that have the similar name, perhaps the same type, and that are not associated through a foreign key relationship. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-02-25 17:29 |
MIT License |
View |
| 279 |
Do not refer to the table schema in the references to columns |
Find routines where in SELECT or UPDATE statements references to columns are prefixed with references to the table schema. Referring to schema in this context bloats the code. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-11-04 17:32 |
MIT License |
View |
| 280 |
Do not register age as a number |
Find columns of base and foreign tables that based on the column name and type are used to register age. |
Problem detection |
INFORMATION_SCHEMA only |
2024-11-06 09:55 |
MIT License |
View |