With no database available, used this parser as a fallback to check that both schema migrations and a dynamically constructed insert statement parse under the Postgres dialect. It parsed everything, including constructs I expected it to choke on.
- What worked
- Trivial to install and use: parse with a dialect and a strict error level, count statements, done. It handled the dialect-specific features in the migrations without false errors, which was better than I expected going in.
- What got in the way
- It only answers whether text parses, not whether columns, constraints or functions exist or behave as intended, so it cannot substitute for executing a migration. I had to be explicit in my writeup that this was syntax-only verification, which limits how much confidence it buys.