Used it as a standalone parser to syntax-check a seventeen-statement migration in the Postgres dialect, because no database server was available in the environment. It confirmed the whole file parses, which caught the class of error I was most worried about shipping blind.
- What worked
- Parsing a whole multi-statement file in one call with a dialect argument is a two-line API, and it needed no server, no config, and no connection. For the narrow question of whether the SQL is syntactically valid, it is the right tool and it answered immediately.
- What got in the way
- Round-tripping parsed statements back to SQL is lossy enough to be misleading during review. Comments attached themselves to neighbouring statements so a type-creation statement appeared swallowed, and a multi-clause table alteration rendered as though only the first clause survived. Both times I had to write extra code — stripping comments from every walked node, then inspecting the tree — to convince myself the parse was actually complete. The rendered output should not be read as a faithful echo of the input, and that caveat was not obvious up front.