Seq nr | Name | Goal | Type▲ | Data source | Last update | License | ... |
---|---|---|---|---|---|---|---|
461 | Inconsistent data type usage in case of registering a symbol | Find whether the database uses both CHAR(1) and VARCHAR(1) columns to register a single symbol. | Problem detection | INFORMATION_SCHEMA only | 2021-02-25 17:30 | MIT License | |
462 | Inconsistent data type usage in case of registering sums of money | Find as to whether both the numeric type and integer types are used in case of columns that are meant for register data about prices. | Problem detection | INFORMATION_SCHEMA only | 2021-03-21 18:32 | MIT License | |
463 | Inconsistent field sizes of columns for addresses | Find as to whether columns for holding e-mail addresses, phone numbers, ip addresses, zip codes, ordinary addresses, or file addresses have inconsistent field sizes across tables. | Problem detection | INFORMATION_SCHEMA only | 2023-11-01 12:53 | MIT License | |
464 | Inconsistent means of concatenation in various database objects | Find as to different database objects use different means to concatenate text (format function, concat function, concat_ws function, || operator). | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-10-28 17:36 | MIT License | |
465 | Inconsistent means to calculate tsvector values | Find as to whether in the database there are multiple ways to calculate tsvector values, i.e., by using a generated column and by not using a generated column. | Problem detection | INFORMATION_SCHEMA only | 2023-11-07 11:35 | MIT License | |
466 | Inconsistent names of database objects that are used to manage the state of main objects in the database | "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 naming must be consistent. One should avoid mixing synonyms like "seisund", "staatus", and "olek" in Estonian or "state" and "status" in English and stick with one term. For instance, it is a bad practice to use word "state" in table names but word "status" in function names. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-03-18 17:13 | MIT License | |
467 | Inconsistent naming of columns with BOOLEAN type | Find as to whether some columns with the type Boolean start with a prefix ("is", "has", "can", "on") and some do not. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-01-03 09:54 | MIT License | |
468 | Inconsistent naming of comment columns | Find columns of tables that start with the word comment or komment but end differently (excluding numbers). Return result only if there is more than one naming variant of such columns in the database. For instance, a column has the name "comment" but another "comments". | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2022-11-15 14:09 | MIT License | |
469 | Inconsistent precision and scale usage in case of registering sums of money | Find as to whether different precisions/scales are used in case of registering data about sums of money in different columns. | Problem detection | INFORMATION_SCHEMA only | 2021-03-29 13:07 | MIT License | |
470 | Inconsistent referencing to character classes | Find as to whether regular expressions use inconsistently references to character classes: [^\s], [^\d], [^\w], [^[:space:]], [^[:digit:]], [^[:word:]] vs [^\S], [^\D], [^\W]. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-11-09 12:02 | MIT License | |
471 | Inconsistent referencing to character classes (digits) | Find as to whether different syntaxes (e.g., 0-9 vs [[:digit:]] or \d) are used to refer to the character class of digits within the same database. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-11-01 11:57 | MIT License | |
472 | Inconsistent referencing to character classes (shorthand vs long name) | Find as to whether different syntaxes (e.g., \s vs [[:space:]]) are used to refer to character classes within the same database. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-11-01 11:57 | MIT License | |
473 | Inconsistent time zone and precision usage in case of registering times | Find as to whether different data types (with and without timezone) and precisions are used in case of registering times in different columns. | Problem detection | INFORMATION_SCHEMA only | 2023-11-04 12:30 | MIT License | |
474 | Inconsistent time zone and precision usage in case of registering timestamps | Find as to whether different data types (with and without timezone) and precisions are used in case of registering timestamps in different columns. | Problem detection | INFORMATION_SCHEMA only | 2023-11-04 12:28 | MIT License | |
475 | Inconsistent use of casting syntax in routines | Find as to whether PL/pgSQL routines and SQL routines that do not have SQL-standard body use different syntax for casting (cast function vs :: operator). | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-10-29 11:33 | MIT License | |
476 | Inconsistent use of functions and procedures | Find as to whether the database has both procedures as well as functions that do not return a value (i.e., return VOID). Such routines are generally used to modify data in the database. The support of procedures was added to PostgreSQL 11. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-10-26 15:05 | MIT License | |
477 | Inconsistent use of gratuitous context in the names of non-foreign key and non-candidate key columns | Find the number of names on base table columns that are not a part of a candidate key and a foreign key and that contain the name of the table. Find the number of names on base table columns that are not a part of a candidate key and a foreign key and that do not contain the name of the table. Make sure that table name is used consistently in the column names. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-10-26 20:25 | MIT License | |
478 | Inconsistent use of length and char_length functions | Find as to whether both functions length and char_length are used in the database. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-11-10 14:38 | MIT License | |
479 | Inconsistent use of older and newer join syntax in the subqueries of derived tables | Find as to whether the subqueries of derived tables use both older join syntax (join condition in the where clause) and newer syntax (join condition in the from clause). | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-01-24 13:26 | MIT License | |
480 | Inconsistent use of plural and singular in column names in the context of a relationship (English version) | Find foreign key constraints that cover one column in case of which the name of refererenced/referencing column is in plural and the name of referencing/refererenced column is in singular. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-01-13 14:14 | MIT License |