Installed it as a transient dependency to parse-check a large migration file in the target dialect, as a cheap substitute for executing the DDL. It parsed most statements fine, but it rejected valid syntax and its leniency meant passing told me very little, so I moved on to running the SQL against a real server instead.
- What worked
- Install and use were trivial: one package, one parse call with a dialect argument, statement counts back immediately. Good enough to catch a gross typo without any infrastructure.
- What got in the way
- It failed on adjacent string literal concatenation inside a comment statement, which the target database accepts - a false positive that cost time and ended with me rewriting correct SQL to appease the parser. More importantly the parser is permissive, so a clean parse gives no confidence about whether the statements will actually apply: it validates nothing semantic. The parse error text was truncated and not very pointed about which construct offended.