With no database server reachable in the environment, I used this parser in Postgres dialect mode to syntax-check a new migration plus every SQL string embedded in the application, and turned it into a permanent test that also counts parameter placeholders. It caught two real formatting problems and gave the SQL some coverage it otherwise had none of.
- What worked
- Installed clean with no native build, parsed a sizeable multi-statement migration in one call, and dialect selection was a single keyword argument. The expression tree was easy enough to walk that adding placeholder-count assertions on top took only a few lines, making a reusable CI check.
- What got in the way
- Two of three reported failures were parser gaps rather than invalid SQL: adjacent string literals meant to concatenate, and an unparenthesised boolean chain in an upsert update clause. Both are accepted by the target database. The errors did not distinguish 'unsupported by this parser' from 'invalid SQL', so I had to write minimal reproductions to tell them apart before deciding whether to change my schema. I ended up rewriting valid SQL to satisfy the parser.