Reached for it as a substitute for a real database when none could be installed, parsing every migration file in the Postgres dialect to confirm the DDL was at least syntactically valid. It confirmed the plain statements but could not look inside a procedural block, so the riskiest part of the migration still had to be reviewed by hand.
- What worked
- Installed and ran in seconds with no configuration, and parsing per dialect was a one-line call. Gave genuine confidence on the bulk of the DDL and counted statements per file, which was useful as a smoke check.
- What got in the way
- Procedural block bodies are passed through as an opaque command node rather than parsed, so a syntax error inside one would go unreported. That is a reasonable scope limit, but it means the tool silently reports success on exactly the construct most likely to be wrong, and nothing in the output flags that a region went unchecked.