| 861 |
Depth of referential tree of a schema |
Depth of referential tree of a database schema is the longest referential path between the tables in this schema (Piattini et al., 2001). In other words, it is the biggest value among the DRT(T) values of all the tables of the schema. |
Sofware measure |
system catalog base tables only |
2020-11-14 15:28 |
MIT License |
View |
| 862 |
Depth of relational tree of a table |
Depth of relational tree of a table T (DRT(T)) is defined by Piattini et al. (2001) as "the longest referential path between tables, from the table T to any other table in the schema". The result may help to classify the data. If the depth is 0, then probably the table contains classifers. Tables with the largest depth probably contain some extra information about main entities. |
Sofware measure |
system catalog base tables only |
2020-11-14 16:13 |
MIT License |
View |
| 863 |
Derived table names have prefix or suffix |
Find the names of views and materialized views that have prefix or suffix. Follow the same naming style as in case of base tables (derived tables are also tables). Thus, if base tables do not have prefixes or suffixes, then derived tables shouldn't have these as well. |
Problem detection |
system catalog base tables only |
2021-02-25 17:29 |
MIT License |
View |
| 864 |
Different foreign key column names in case of referencing the same candidate key |
Find the cases when the names of columns in different foreign keys that reference to the same candidate key are different. If different names reflect different roles, then it is legitimate. However, there could also be accidental differences that makes it more difficult to use the database. |
Problem detection |
system catalog base tables only |
2021-03-12 11:21 |
MIT License |
View |
| 865 |
Different prefixes of a candidate key column and a referencing foreign key column |
The naming must be consistent. Find foreign key constraints where the candidate key column and foreign key column names have different prefixes. Thus, for instance, one cannot use USING syntax for joining the tables. |
Problem detection |
system catalog base tables only |
2021-02-25 17:29 |
MIT License |
View |
| 866 |
Different suffixes of a candidate key column and a referencing foreign key column |
The naming must be consistent. Find foreign key constraints where the candidate key column and foreign key column names have different suffixes. Thus, for instance, one cannot use USING syntax for joining the tables. |
Problem detection |
system catalog base tables only |
2021-02-25 17:29 |
MIT License |
View |
| 867 |
Different tasks of rules |
Find different tasks that are solved by using rules, i.e., different rules on the same table or different tables that do the same thing are considered to solve one task. |
General |
system catalog base tables only |
2024-01-14 16:10 |
MIT License |
View |
| 868 |
Disabled rules |
Identify disabled rules. These should be enabled or dropped, otherwise these are dead code. |
Problem detection |
system catalog base tables only |
2022-10-21 11:22 |
MIT License |
View |
| 869 |
Disabled system triggers (i.e., disabled enforcement of constraints) |
These triggers should be enabled because otherwise some important functionality regarding constraints like enforcing referential integrity does not work. |
Problem detection |
system catalog base tables only |
2021-03-12 15:06 |
MIT License |
View |
| 870 |
Disabled user triggers |
Identify disabled triggers. These should be enabled or dropped, otherwise these are dead code. |
Problem detection |
system catalog base tables only |
2021-02-25 17:30 |
MIT License |
View |
| 871 |
Do not always depend on one's parent |
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. |
General |
system catalog base tables only |
2021-03-12 15:36 |
MIT License |
View |
| 872 |
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 |
| 873 |
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 |
| 874 |
Duplicate foreign key constraints |
Find duplicate foreign key constraints, which involve the same columns and refer to the same set of columns. |
Problem detection |
system catalog base tables only |
2021-02-25 17:30 |
MIT License |
View |
| 875 |
Duplicate independent (i.e., not created based on a table) composite types |
Find composite types with the same attributes (regardless of the order of attributes). Make sure that there is no duplication. |
Problem detection |
system catalog base tables only |
2021-02-25 17:29 |
MIT License |
View |
| 876 |
Duplicate keys |
Find completely overlapping key (primary key and unique) constraints. This is a form of duplication. It leads to the creation of multiple indexes to the same set of columns. |
Problem detection |
system catalog base tables only |
2021-10-16 10:27 |
MIT License |
View |
| 877 |
Duplicate materialized views |
Find materialized views with exactly the same subquery. There should not be multiple materialized views with the same subquery. Do remember that the same task can be solved in SQL usually in multiple different ways. Thus, the exact copies are not the only possible duplication. |
Problem detection |
system catalog base tables only |
2021-02-25 17:30 |
MIT License |
View |
| 878 |
Duplicate non-fuction based unique indexes |
Find pairs of non-function based unique indexes that cover the same set of columns. Include indexes that support a constraint (primary key, unique, exclude), i.e., these indexes have been automatically created due to the constraint declaration. For instance, it helps us to find unique indexes that have been defined to already unique columns. |
Problem detection |
system catalog base tables only |
2022-10-21 10:17 |
MIT License |
View |
| 879 |
Duplicate rules |
Find multiple rules with the same definition (event, condition, action) on the same table. Do remember that the same task can be solved in SQL usually in multiple different ways. Thus, the exact copies are not the only possible duplication. |
Problem detection |
system catalog base tables only |
2021-02-25 17:30 |
MIT License |
View |
| 880 |
Empty tables |
Find base tables where the number of rows is zero. If there are no rows in a table, then it may mean that one hasn't tested constraints that have been declared to the table or implemented by using triggers. It could also mean that the table is not needed because there is no data that should be registered in the table. |
Problem detection |
system catalog base tables only |
2022-10-21 15:55 |
MIT License |
View |