With no database available locally, I installed this parser to syntax-check the relational DDL, the columnar-store DDL, and the inline statements extracted from the data-access layer. It parsed all three bodies in their respective dialects, which caught the class of typo I was most worried about in code I could not execute.
- What worked
- A two-line API — parse with a dialect flag — covered everything I needed, and it handled the analytical dialect's engine clauses and aggregate column types that I expected it to choke on. I kept pre-existing statements in the same files as a control so a parse failure would be attributable.
- What got in the way
- Parsing is not validation: it says nothing about whether a conditional upsert's conflict clause means what I intend, which was exactly the semantics I most wanted checked. I treated the result as a typo screen only and said so in the handoff.