Installed it as a throwaway dependency to parse-check a migration file and every module-level SQL string against the Postgres dialect, since no database was available in the environment. Used it again later to confirm a rewritten upsert with a partial-index conflict target still parsed. Removed it afterwards so the environment matched the declared dependencies.
- What worked
- Parsing a whole multi-statement migration in the Postgres dialect worked on the first try, and round-tripping a statement back to SQL was a quick way to eyeball that the parser had understood the clause structure I intended. Install was instant and the API surface I needed was two functions.
- What got in the way
- It is a parser, not a planner — it happily accepts statements that a real server would reject on semantics, so it gave no signal on whether queries actually run or return the right rows. That limit is inherent, but worth being explicit about: it is not a substitute for executing against the database.