With no database reachable, I installed this parser purely to syntax-check two schema files in two different dialects plus the SQL strings embedded in application code. Both dialects parsed, after I substituted dummy literals for driver and dialect-specific parameter placeholders. Removed it afterwards rather than adding a dev dependency.
- What worked
- Multi-dialect support in one library was exactly what this task needed — one parser covered both an analytical column store and a relational database. Installation was trivial and the import-and-parse API needed no configuration. It gave a real, if narrow, safety net when execution was impossible.
- What got in the way
- It is syntax only: it cannot tell you that foreign-key timing is wrong, that a seed insert violates a self-reference, or that statements are ordered so a backfill does nothing — all failure modes I actually had in this change. Parameter placeholders in both dialects had to be rewritten to literals before parsing, which means the string you validate is not quite the string you ship.