{"id":13856,"date":"2025-03-18T21:31:42","date_gmt":"2025-03-18T20:31:42","guid":{"rendered":"https:\/\/www.salvis.com\/blog\/?p=13856"},"modified":"2025-03-18T22:00:51","modified_gmt":"2025-03-18T21:00:51","slug":"dblinter-rules-repository","status":"publish","type":"post","link":"https:\/\/www.salvis.com\/blog\/2025\/03\/18\/dblinter-rules-repository\/","title":{"rendered":"dbLinter Rules Repository"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

Today I proudly announce that the Joint Venture between United Codes <\/a>and Grisselbav<\/a> released the initial version of the dbLinter Rules Repository website<\/a>. This is the first publicly available component of the dbLinter tool suite.<\/p>\n\n\n\n

What is dbLinter?<\/h2>\n\n\n\n

dbLinter is a suite for checking and improving the quality of database applications. Quality is assessed using static code analysis and database queries based on a configuration. A configuration is primarily centrally managed. It contains file patterns, rules, validators, SQL-based tests, parameters, and connect information for read-only database access within checks and tests.<\/p>\n\n\n\n

Is it Free?<\/h2>\n\n\n\n

dbLinter is a commercial and subscription-based product. However, there are two free subscription plans foreseen. Anonymous<\/strong> without registration and Free<\/strong> requiring registration with a valid email address. You need a login to manage configurations.<\/p>\n\n\n

\n\t\t\t
\n\t\t\t\t<\/colgroup>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

<\/p>\n<\/div><\/th>\n\n

\n

Anonymous<\/p>\n<\/div><\/th>\n\n

\n

Free<\/p>\n<\/div><\/th>\n\n

\n

Essential<\/p>\n<\/div><\/th>\n\n

\n

Professional<\/p>\n<\/div><\/th>\n<\/tr>

\n

Number of seats<\/p>\n<\/div><\/td>\n\n

\n

unlimited<\/p>\n<\/div><\/td>\n\n

\n

1<\/p>\n<\/div><\/td>\n\n

\n

1-n<\/p>\n<\/div><\/td>\n\n

\n

1-n<\/p>\n<\/div><\/td>\n<\/tr>

\n

Number of configurations<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

1<\/p>\n<\/div><\/td>\n\n

\n

unlimited<\/p>\n<\/div><\/td>\n\n

\n

unlimited<\/p>\n<\/div><\/td>\n<\/tr>

\n

View rules and related data<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Manage configurations<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Run checks<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Run SQL-based tests<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

dbLinter VS Code extension<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Run all accessible checks and tests<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Quick fixes in dbLinter VS Code extension<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Ignore chosen SQL-based test findings<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

dbLinter CLI with SonarCloud integration<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Manage user access<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

dbLinter SonarQube plugin<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Access to dbLinter test repository<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Custom rules, checks and SQL-based tests<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Generate Java project for checks and SQL-based tests<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Manage custom validators (plugins)<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Export rules and configurations<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr>

\n

Import rules and configurations<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

–<\/p>\n<\/div><\/td>\n\n

\n

yes<\/p>\n<\/div><\/td>\n<\/tr><\/tbody><\/table>\n\t\t\t<\/div>\n\t\t<\/div>\n\n\n

And of course, access to the dbLinter Rules Repository website<\/a> is also free.<\/p>\n\n\n\n

What Are the Rules Based on?<\/h2>\n\n\n\n

Most of the rules are taken over from the decommissioned Trivadis PL\/SQL & SQL Coding Guidelines<\/a>. The origin is documented per rule under the Reference<\/code> section. See for example G-1080: Avoid using the same expression on both sides of a relational comparison operator or a logical operator<\/a>. This rule exists in 4 different rule repositories.<\/p>\n\n\n\n

Over 180 Rules – This is Ridiculous!<\/h2>\n\n\n\n

You do not need to enable all rules. I compare it to a breakfast buffet. You pick what you like and how much you want.<\/p>\n\n\n\n

Furthermore, not all rules have the same severity. The most important rules are marked as Blocker<\/a>. Pick some of these to start with.<\/p>\n\n\n\n

What’s Next?<\/h2>\n\n\n\n

Coding guidelines are really helpful, especially if you can use them to review your code automatically while it’s being developed in your favourite IDE. Of course you want them also as part of a CI\/CD pipeline. However, finding problems while typing code is far more efficient.<\/p>\n\n\n\n

Therefore the next component will be a VS Code extension. Here’s an example of how it will look like:<\/p>\n\n\n\n