rules repository

dbLinter rules repository

Explore dbLinter rules for Oracle Database, Oracle APEX and PostgreSQL. Each rule explains what it checks and why, with code examples and configuration options to match your standards.

dbLinter analyses SQL, PL/SQL and PL/pgSQL code and tests your data model, with quick fixes where available, right in VS Code.

Browse all rules Get the VS Code extension

Pick a profile

Each level includes every rule of the levels above it.

  1. Level 1 Essential No-brainer, universal agreement. 63 rules (+63)
  2. Level 2 Balanced Good practice, low controversy. 97 rules (+34)
  3. Level 3 Strict Advanced, medium controversy. 171 rules (+74)
  4. Level 4 Aggressive Opinionated, high controversy. 206 rules (+35)
  5. Level 5 Extreme Merciless, includes everything. 229 rules (+23)

Recently added

RSS feed

31 new this month and last month.

What's new: all 46 rules added since launch →

Get started with dbLinter

VS Code extension
Install it and lint your SQL and PL/SQL code in the editor.
dblinter.app
Choose active rules, override severities and set parameters, e.g. naming conventions.
Getting started video
Setup and configuration, walked through by Philipp Hartenfeller.
Features & pricing
What dbLinter offers and the available plans.

Using VSCodium or another Open VSX editor? Get the extension from the Open VSX Registry.

Browse by

Quality Areas
Maintainability, reliability and security.
Tags
Topics such as naming, performance or exceptions.
SonarQube Severities
From blocker to info.
Fixing Times
How much effort a finding takes to fix.

What is dbLinter?

dbLinter checks database applications against a configurable set of rules, using static code analysis and database queries. It covers Oracle Database and PostgreSQL in files with SQL, PL/SQL, PL/pgSQL, SQL*Plus, SQLcl and psql, and ships tests that validate your data model, for example tables without primary keys or foreign keys without an index. Quick fixes are offered where available, findings can be ignored, and you can add your own rules, checks and tests.

Coming from the Trivadis PL/SQL & SQL Coding Guidelines or the discontinued db* CODECOP? Many rules will look familiar: rule pages link the Trivadis original where there is one.