| 941 | PUBLIC has TEMPORARY privilege in the database | Find as to whether PUBLIC (all current and future users) has TEMPORARY privilege in the database. PUBLIC gets the privilege by default. | Problem detection | system catalog base tables only | 2021-12-31 15:52 | MIT License | |
| 942 | Recursive relationships with the same source and target | Find incorrectly implemented adjacency lists. | Problem detection | system catalog base tables only | 2021-02-25 17:30 | MIT License | |
| 943 | Recursive rules that directly modify their home table | Do not cause potentially infinite loops. Recursive rules would fire itself over and over again. Although the system is able to detect these after executing a data modification statement it is better to avoid creating these altogether. | Problem detection | system catalog base tables only | 2022-10-21 15:59 | MIT License | |
| 944 | Redundant indexes | Find indexes that may be redundant. In addition to identical indexes it also considers indexes that cover the same columns and have the same properties except uniqueness. The query considers all types of indexes, including indexes that have been automatically created to support a constraint and function-based indexes. | Problem detection | system catalog base tables only | 2021-02-25 17:29 | MIT License | |
| 945 | Referential degree of tables (ver 2) | Find how many base tables are referenced from a base table by using foreign keys. | Sofware measure | system catalog base tables only | 2021-03-12 11:06 | MIT License | |
| 946 | Rules with the same name in different schemas | Find rule names that are used in a database in more than one schema. Different things should have different names. But here different rules have the same name. Also make sure that this is not a duplication. | General | system catalog base tables only | 2020-11-06 14:51 | MIT License | |
| 947 | Rules with the same name within the same schema | Find names of rules that are used within the same schema more than once. Give different triggers different names. | Problem detection | system catalog base tables only | 2021-02-25 17:30 | MIT License | |
| 948 | Sequences that are not owned by a table column | Find sequence generators that are not owned by a table column, i.e., if one drops the table or the column, then the sequence generator stays in place. | Problem detection | system catalog base tables only | 2023-10-06 14:40 | MIT License | |
| 949 | Short cycle (columns) | Find cases where two candidate keys of the same table that are also foreign keys reference to each other. | Problem detection | system catalog base tables only | 2021-11-28 02:08 | MIT License | |
| 950 | Simple primary keys that column name does not contain the table name | Find simple primary keys that column name does not contain the table name. The naming should be clear and consistent. | Problem detection | system catalog base tables only | 2023-03-19 10:35 | MIT License | |
| 951 | System-generated table constraint names (constraints that involve one column) | Find the names of database constraints that have been system-generated. Additional restrictions are that the constraints must involve only one column and are associated directly with a table (not through a domain). Names should follow the same style. If there is a mix of system-generated and user-defined names, then the style is most probably different. | Problem detection | system catalog base tables only | 2021-12-10 12:47 | MIT License | |
| 952 | Table constraints with the cardinality bigger than one | Find constraints that involve more than one columns. Check as to whether the names follow a common style or not. | General | system catalog base tables only | 2020-11-19 13:34 | MIT License | |
| 953 | Table constraints with the same name (constraints connected directly with a base table or a foreign table) | Find base table and foreign table constraint names that are used in a database more than once (possibly in different schemas or in case of different types of constraints). Different things should have different names. But here different constraints have the same name. Also make sure that this is not a sign of duplication. | Problem detection | system catalog base tables only | 2022-11-15 16:43 | MIT License | |
| 954 | Table inheritance | Find inheritance between base tables. Use table inheritance carefully because, for instance, certain constraints are not inherited and must be redefined on child tables. | General | system catalog base tables only | 2020-11-15 13:02 | MIT License | |
| 955 | Table inheritance (path view) | Find in case of each base table that participates in a table inheritance hierarchy the path to the table from the top-level table. Use table inheritance carefully because, for instance, certain constraints are not inherited and must be redefined on child tables. Also make sure that the identifier of each child table in an inheritance hierarchy is a hyponym of the identifier of its parent table. | General | system catalog base tables only | 2022-11-13 16:13 | MIT License | |
| 956 | Tables that have associated user triggers | Find information about tables that are associated with triggers. | General | system catalog base tables only | 2020-11-06 14:51 | MIT License | |
| 957 | The longest referential paths | Find the longest referential paths between the tables regardless of the schema that contain the tables. | Sofware measure | system catalog base tables only | 2020-11-14 15:42 | MIT License | |
| 958 | The name of the base table that implements a binary relationship type does not explain the meaning of the relationship | Find base tables that implement a binary relationship type (have two foreign keys) and the name of the table consist of the names of tables that this (intermediate) table connect. The names should be derived from the domain. For instance, instead of name Course_Lecturer it is better to have name Teaching. | Problem detection | system catalog base tables only | 2023-03-18 17:58 | MIT License | |
| 959 | The number of compensating actions of foreign key constraints | Find the number of compensating actions that are specified in case of foreign key constraints. | Sofware measure | system catalog base tables only | 2020-11-16 10:11 | MIT License | |
| 960 | The number of direct and indirect child tables (foreign keys) | Find the number of direct and all (direct+indirect) child tables of a base table based on the foreign keys. The result may help to classify the data. If the number of direct children is small but the number of all children is large, then the table probably contains classifiers. If both the number of direct and all children is large, then the table probably contains master data. If the number of all children is small, then the table probably contains transactional data, logs, or descriptive information of main entities. | Sofware measure | system catalog base tables only | 2020-11-14 16:10 | MIT License | |