| 821 |
Three-valued logic (non-Boolean columns) |
Find non-foreign key columns of base tables that probably (based on the column name) contain values that represent truth values but do not have NOT NULL constraint. Use two-valued logic (TRUE, FALSE) instead of three-valued logic (TRUE, FALSE, UNKNOWN). Because NULL in a Boolean column means unknown make all the columns mandatory. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-03-20 14:07 |
MIT License |
View |
| 822 |
Too few rounds in case of calculating the hash |
Find user-defined routines where gen_salt function is used with the number of rounds that is smaller than 12. The number should be adjusted based on the hardware where the system resides. Password hashing should take at least 250 ms. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-10-25 17:21 |
MIT License |
View |
| 823 |
Too generic names (candidate key columns) |
Find candidate key columns with the names like id, identifikaator, code, kood, number, etc. The names should have a prefix or a suffix. These are too generic names. |
Problem detection |
system catalog base tables only |
2023-01-20 12:35 |
MIT License |
View |
| 824 |
Too generic names (columns) |
Find the names of columns that are too generic. In SQL databases data/information is represented as values in columns. It is not a good style to use generic words like data, information, column, etc. In the names of columns. Moreover, avoid too generic column names like: id, tyyp, kood, aeg, kp,type, code, time, date, fk, pk. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2025-05-03 13:51 |
MIT License |
View |
| 825 |
Too generic names (columns) (there is a column with a more specific name in the table) |
Find column names in case of which the same table has another column (with more specific name) that name contains the column name in the end or in the beginning. For instance, a base table has columns parent and root_parent and the former col-umn name is too generic, i.e., it should be more specific. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-03-20 01:01 |
MIT License |
View |
| 826 |
Too generic names (domain constraints) |
Find domain CHECK constraints that have a too generic name - for instance, the name contains word "data" ) or the name is an abbreviation of the constraint type name (for instance, "chk" or "chk1"). |
Problem detection |
INFORMATION_SCHEMA only |
2021-10-31 17:39 |
MIT License |
View |
| 827 |
Too generic names (foreign key columns) |
Find foreign key columns with the names like id, identifikaator, code, kood, number, etc. The names should have a prefix or a suffix that describes the nature of relationship with the referenced table or at least referes to the referenced table. These are too generic names. |
Problem detection |
system catalog base tables only |
2023-01-20 12:37 |
MIT License |
View |
| 828 |
Too generic names (parameters) |
Find the names of parameters that are too generic. The routines work with data/information. Thus, it is not a good style to use generic words like data, information, parameter, etc. In the names of parameters. Moreover, avoid too generic parameter names like: id, tyyp, kood, aeg, kp,type, code, time, date, fk, pk, param. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2025-05-03 13:54 |
MIT License |
View |
| 829 |
Too generic names (parameters) (there is a parameter with a more specific name in the routine) |
Find parameter names in case of which the same routine has another parameter with the same mode but with more specific name, i.e., the name contains the parameter name in the end or in the beginning. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-06 12:03 |
MIT License |
View |
| 830 |
Too generic names regarding persons and their names (columns of derived tables) |
Find derived table columns that name refers to the possibility that these contain person names. The names of derived table columns that contain person names should refer to the role that the corresponding entity type has in the view. For instance, if view active_product has a column with the name surname, then the column name does not give information what is the role of the person in the context of the view. Better name would be, for instance, registrator_surname. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2022-11-10 14:25 |
MIT License |
View |
| 831 |
Too generic names (routines) |
"Avoid using the same word for two purposes. Using the same term for two different ideas is essentially a pun" (Robert C. Martin, Clean Code) Do not use the Estonian words like 'lisa', 'muuda', 'kustuta' or the corresponding English words 'add', 'delete', 'update' as the names of routines because it would make the code much less understandable. What is the task of the routine f_add? Register people? Register orders? What? Do not refer to the generic concepts like data and information because all routines work with these. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-01-07 20:38 |
MIT License |
View |
| 832 |
Too generic names (table constraints) |
Find table constraints (constraints that are associated directly with the table) that have too generic names like "key" or the name contain too generic words like "data" (all constraints restrict data in the table), or the name is an abbreviation of a constraint type name. |
Problem detection |
system catalog base tables only |
2025-05-05 07:02 |
MIT License |
View |
| 833 |
Too generic names (tables) |
Find the names of tables that are too generic. In SQL databases data/information is represented as values in columns. It is not a good style to use generic names like table, data, information, list etc. in the names of tables. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-01-07 20:37 |
MIT License |
View |
| 834 |
Too generic names (unique index columns) |
Find unique index (not associated with a constraint) columns with the names like id, identifikaator, code, kood, number, etc. The names could have underscores as the prefix or suffix. These are too generic names. |
Problem detection |
system catalog base tables only |
2023-01-07 20:34 |
MIT License |
View |
| 835 |
Too generic names (unique indexes) |
Find unique indexes that have too generic names like "key" or the name contain too generic words like "data" (all constraints restrict data in the table), or the name is an abbreviation of a constraint type name. |
Problem detection |
system catalog base tables only |
2023-01-08 10:38 |
MIT License |
View |
| 836 |
Too generic names (user-defined types, domains) |
Find names of user-defined types and domains that contain too generic (noise) words. |
Problem detection |
system catalog base tables only |
2021-10-31 17:41 |
MIT License |
View |
| 837 |
Too many slashes in regular expressions |
Find patterns of regular expressions where more than \ is written instead of \, e.g., \\s is used instead of \s to refer to a character class. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2024-12-21 11:15 |
MIT License |
View |
| 838 |
Too short domain constraint names |
Find names of domain constraints that are shorter than the length of the name of the domain + two characters. |
Problem detection |
INFORMATION_SCHEMA only |
2021-02-25 17:29 |
MIT License |
View |
| 839 |
Too short names of database objects |
"Names in software are 90 percent of what make software readable. You need to take the time to choose them wisely and keep them relevant. Names are too important to treat carelessly. Names should not cause confusion." (Robert C. Martin, Clean Code) The names should be meaningful and searchable. Find the names (identifiers) of user-defined database objects that are shorter than three characters. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2024-12-21 17:27 |
MIT License |
View |
| 840 |
Too short or missing comments of derived tables and routines |
Find views, materialized views, and user-defined routines that do not have a comment at all or the comment is shorter than twice the length of the object name, or the comment states that it is missing (TODO). You should give information to future developers and maintainers of the system (including the future version of yourself). Do not just repeat the name in the comment (with perhaps some rewording). |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-01-19 12:56 |
MIT License |
View |