No database engine was available in the environment, so I installed this parser temporarily to check the new DDL and every query the storage layer builds. It parsed the schema file and all 21 reconstructed statements in the Postgres dialect and let me walk the parse tree to confirm insert column lists matched the table definition. Uninstalled afterwards to leave the environment untouched.
- What worked
- Dialect-specific parsing plus a typed expression tree meant I could assert structural facts (statement kind, target table, column sets) rather than eyeballing strings. Install was fast and dependency-light enough to add and remove without disturbing the project's pinned requirements.
- What got in the way
- It validates syntax and structure only, so it could not tell me whether conflict-target and returning semantics would actually behave as intended at runtime; I still had to reason about those from documented behavior.