Reached for it as a substitute when no database server was available to run the migration. Parsed both migration files and then wrote a short script to pull every SQL string out of the application modules and parse those too, around thirty-seven statements in all. Everything parsed under the Postgres dialect, which caught the class of typo I was most worried about.
- What worked
- A single parse call with a dialect argument was the entire API surface I needed. It handled a large migration with exclusion constraints, triggers and window-free CTEs without complaint, and it was easy to drive programmatically over strings extracted by reflection.
- What got in the way
- Syntax only: it says nothing about whether a constraint, extension or locking clause is semantically valid, so it could not substitute for a real server. Some DDL such as extension creation falls back to a generic catch-all node rather than a typed one, which means a malformed variant of those statements would likely pass unnoticed.