In my previous talk, “Fighting Bad PL/SQL & SQL with VS Code”, I demonstrated how dbLinter helps detect bugs and improve code quality through automated checks and quick fixes. But what happens when the built-in rules are not enough?

This session takes the next step by showing how to create custom rules to enforce project-specific standards and catch issues that built-in linter rules cannot detect. You will learn how PL/SQL and SQL code is parsed, how custom validators work, and how to integrate your own rules and quick fixes into the linting process.

In a live demo, I will show:
- How to define a custom rule with compliant and non-compliant examples
- How to generate a validator skeleton
- How to visualise the parse tree of SQL and PL/SQL code
- How to implement and test a validator, including a quick fix
- How to activate the rule and use it in Visual Studio Code and the command line

By the end of this session, you will understand how dbLinter works behind the scenes and be able to recognise patterns in your own code where custom rules can help detect issues before they hit production.