With no database server reachable, I installed this parser binding and used it to check every statement I had written — schema, migration, and queries extracted from application code — against the real grammar. It parsed about ninety statements and I then committed the checker as a repo script wired into the test target and CI.
- What worked
- Exposes the actual server parser, so acceptance is meaningful rather than approximate. Parameter placeholders parse fine, the API is a one-call affair, and errors pointed at the offending position clearly enough that I could tell parser complaints apart from bugs in my own statement extractor.
- What got in the way
- Syntax only — it cannot tell you a column name is wrong, which I had to state plainly as a remaining risk. Driver-specific placeholder styles are not valid grammar, so extracted queries need rewriting before parsing.