Reached for this first to parse-check migration files with no database available. It parsed the top-level statements cleanly, but every procedural function body is just a string literal to it, so the part I actually needed verified went unchecked and I moved to a lower-level binding instead.
- What worked
- Install and use were trivial and the parse call over whole migration files returned promptly with no setup beyond an async module load.
- What got in the way
- No way to descend into stored-procedure bodies — the exported surface offers parse/deparse only. For a migration whose risk is concentrated in procedural code, a clean result here is close to meaningless, and nothing in the API signals that limitation.