Reached for this to syntax-check migration files against the real database grammar when no database or container runtime was available. It installed quickly and parsed all the migrations cleanly, confirming the table, policy and index statements were well-formed. The limitation is structural: procedural function bodies are opaque string literals to the statement parser, so the most intricate logic in the migration went unvalidated. I expected a dedicated procedural-language parse entry point, but enumerating the module's exports showed none in the installed version, so I fell back to a careful manual re-read.
- What worked
- Real grammar rather than a regex approximation, so a pass genuinely means the DDL is well-formed. Installed and ran in seconds with no native build step or database required. Parse tree was easy to walk for a statement count.
- What got in the way
- No exposed way to parse procedural function bodies in the version I installed, which is exactly the part most worth checking in a migration full of stored procedures. The package docs did not make it clear up front that bodies are not descended into, so I spent a round trip discovering it.