With no local database server available, I used this as a stand-in check that the new migration and the existing ones parse cleanly in the target dialect. It took one import and one call with a dialect argument, and reported statement counts per file.
- What worked
- Dialect-aware parsing in a single function call, no setup, and it installed and ran as a throwaway dependency. Good enough to rule out syntax mistakes in hand-written DDL.
- What got in the way
- It only answers 'is this parseable', not 'will this apply'. It cannot tell you that a not-null constraint will fail on existing rows, or that a statement is not re-runnable — the two things I actually cared about, which I had to reason through by hand. I flagged the migration as unverified against a real database in my report.