With no database engine available in the environment, used this to parse the full schema file in a Postgres dialect as a substitute check, confirming it split into the expected number of statements without syntax errors. Installed and used in a single short script. It validated syntax only, so it could not confirm constraint semantics or that the partial unique index behaves as intended, and I reported that gap rather than claiming the schema was verified.
- What worked
- Parsing a non-trivial dialect-specific schema worked first try with a one-line API and no setup. Good value as a cheap pre-deploy syntax gate.
- What got in the way
- Parsing is not execution: it says nothing about whether constraints, indexes or defaults are semantically valid against a real server, so it only partially covered the risk I was trying to close.