| 501 | Names of database objects (regular identifiers) that contain $ | Find names (identifiers) of user-defined database objects that are regular identifiers and contain the $ sign starting from the second position. "Note that dollar signs are not allowed in identifiers according to the letter of the SQL standard, so their use might render applications less portable." (PostgreSQL manual) | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:46 | MIT License | |
| 502 | Names of database objects that are fully uppercase | Full uppercase means screaming and it makes comprehending the names more difficult. Find the names (identifiers) of user-defined database objects that are fully uppercase. Because PostgreSQL stores regular identifiers lowercase in the system catalog it also means that these are delimited identifiers, i.e., these are case sensitive. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 17:27 | MIT License | |
| 503 | 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. | General | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 17:23 | MIT License | |
| 504 | Names of database objects that contain a digit | Find the names (identifiers) of user-defined database objects that contain at least one digit. Names should be informative. Duplicates should be avoided. Digits in names are a possible sign of duplication of database objects or unclear names. | General | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:45 | MIT License | |
| 505 | Names of database objects that contain dollar sign | Find names of database objects that contain a dollar sign ($) that is not the first symbol of the name. In PostgreSQL regular identifiers cannot start with $. However, $ can be used in other positions of the name. "Note that dollar signs are not allowed in identifiers according to the letter of the SQL standard, so their use might render applications less portable." (PostgreSQL documentation) | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:43 | MIT License | |
| 506 | Names of database objects that contain two or more consecutive underscores or spaces as separators of name components | Improve the readability of names. Find the names (identifiers) of user-defined database objects that contain two or more consecutive underscores or spaces that separate name components, i.e., these are not at the beginning and in the end of the name. Example of such names are person__id or "person id". Names with duplicate underscores use snake case style but duplication of underscores does not improve the usability of the name. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 17:22 | MIT License | |
| 507 | Names of database objects that end with an underscore | Find names of database objects that end with a underscore. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:42 | MIT License | |
| 508 | Names of database objects that mix snake_case and camelCase/PascalCase | Use consistent style of naming. Prefer snake_case. Regular identifiers are stored in the PostgreSQL system catalog in lowercase. Thus, if you use, for instance the identifier thisIsLongTableName, then, for instance,in the pg_dump result you will see the table name thisislongtablename. If the name in the system catalog is thisIsLongTableName, then it means that the name is a delimited identifier, i.e., case sensitive. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:35 | MIT License | |
| 509 | Names of database objects that perhaps end with a sequence number | Find the names (identifiers) of user-defined database objects that end with one or more digit. Names should be informative. Duplicates should be avoided. Digits in names are a possible sign of duplication of database objects or unclear names. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:33 | MIT License | |
| 510 | Names of database objects that perhaps end with a sequence number (aggregate view) | Find the number of names (identifiers) of user-defined database objects that end with one or more digit. Names should be informative. Duplicates should be avoided. Digits in names are a possible sign of duplication of database objects or unclear names. | Sofware measure | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:33 | MIT License | |
| 511 | Names of database objects that start with an underscore | Improve the readability of names. Find the names (identifiers) of user-defined database objects that start with an underscore. This is not necessarily a mistake. For instance, parameter names could start with an underscore. On the other hand, it could be that the prefix is missing in the name. | General | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 17:23 | MIT License | |
| 512 | Names of database objects with four or more consecutive identical symbols | Find names of database objects with four or more consecutive identical symbols | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 17:27 | MIT License | |
| 513 | Names of database objects with perhaps too many digits | Find the names of database objects where more than half the signs are digits. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 17:20 | MIT License | |
| 514 | Names of database objects with perhaps too many subcomponents (terms) | "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 number of subcomponents (terms) should not be too big. Find the names (identifiers) of user-defined database objects that perhaps contain too many subcomponents, assuming, that the separator of the components is "_". | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 16:44 | MIT License | |
| 515 | Names of database objects with perhaps too many subcomponents (terms) that consist of only consonants | Find names of database objects where the number of subcomponents (terms) that consist of only consonants is bigger than the number of subcomponents that contain at least one vowel. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2024-12-21 17:18 | MIT License | |
| 516 | Names of indexes that do not contain the table name | Find indexes that do not support a declarative constraint and that are perhaps badly named. Table names make the names more expressive and user-friendly. | Problem detection | system catalog base tables only | 2023-01-10 18:13 | MIT License | |
| 517 | Names of the columns of derived tables that have been given by the system | Find columns of derived tables that name has been given by the system. The creators of the table should specify the name themselves to avoid ugly names and nasty surprises. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2022-11-15 16:48 | MIT License | |
| 518 | Names of the password columns | Find names of columns of base tables, views, and materialized views that contain passwords. Make sure that the naming is consistent, | General | INFORMATION_SCHEMA+system catalog base tables | 2022-11-30 15:04 | MIT License | |
| 519 | Names of triggers and rules that do contain the table name | The names should contain table name in order to make the names better understandable. | General | INFORMATION_SCHEMA+system catalog base tables | 2023-01-13 19:23 | MIT License | |
| 520 | Names of triggers and rules that do not contain the table name | The names should contain table name in order to make the names better understandable. | Problem detection | INFORMATION_SCHEMA+system catalog base tables | 2023-01-13 19:18 | MIT License | |