With no database server available locally or in CI, I used this library's embedded upstream SQL parser to syntax-check a large hand-written migration plus every SQL string in the application modules, then wired that check into the test suite as a permanent guard. It caught the main risk class in hand-written SQL and turned an entirely unchecked part of the codebase into something CI can verify.
- What worked
- Installed cleanly and parsed a fairly exotic migration (exclusion constraints, triggers, data-modifying CTEs, upserts) without complaint. A single parse call over file text was all the API I needed. Prebuilt wheels existed for the CI interpreter version, so no source build.
- What got in the way
- It is a pure grammar check, so semantic and catalog errors still pass. Driver parameter placeholders are not valid SQL on their own, so I had to substitute them before parsing while preserving casts — a small preprocessing step the docs did not hint at.