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.
Pick a profile
Each level includes every rule of the levels above it.
-
Level 1 Essential No-brainer, universal agreement. 63 rules (+63)
-
Level 2 Balanced Good practice, low controversy. 97 rules (+34)
-
Level 3 Strict Advanced, medium controversy. 171 rules (+74)
-
Level 4 Aggressive Opinionated, high controversy. 205 rules (+34)
-
Level 5 Extreme Merciless, includes everything. 228 rules (+23)
Recently added
RSS feed30 new this month and last month.
- A-0980 New Try to set the compatibility mode to the latest version.
- A-1070 New Always reload pages with editable Interactive Grids only for success.
- A-1390 New Avoid buttons defined by dynamic action without a dynamic action.
- A-2430 New Avoid page items without a label template.
- A-3070 New Try to define a default value for Interactive Grid checkbox and switch columns.
Get started with dbLinter
Using VSCodium or another Open VSX editor? Get the extension from the Open VSX Registry.
Browse by
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.