core: analyze every dialect through the new analysis core

[kyleconroy]

sqlc analyze ran ClickHouse and GoogleSQL on the core catalog and analyzer while PostgreSQL, MySQL and SQLite still went through the legacy compiler. This routes all five dialects through the core.

What changed

• compiler: NewCompiler takes options; WithCoreAnalysis, which the analyze command passes, builds a core catalog seeded with the engine's dialect and skips the legacy catalog and the analyzer connection entirely. ClickHouse and GoogleSQL keep doing so unconditionally. generate, vet and compile are untouched.
• internal/core/seed: a declarative description of a dialect — its types and their aliases, the operators and casts between them, and the functions it ships with — that Apply turns into catalog rows. The PostgreSQL, MySQL and SQLite seeds are built on it and reuse each engine's existing function catalog (pg_catalog, and the MySQL and SQLite stdlibs), so count, max, upper and friends resolve with real return types.
• internal/core: literals take the type each dialect names rather than PostgreSQL's (the analyzer hardcoded int4/numeric/text/bool, which only PostgreSQL has); a type a schema declares — an enum, or one of SQLite's free-form type names — gains the dialect's comparison operators; array types are named after their element.
• internal/core/schema: enums, functions, views, CREATE TABLE AS, ALTER TABLE and the rename statements now load into the catalog, and a column's array-ness is read from either the type name or the column. Five new catalog queries back the ALTER TABLE mutations, generated by sqlc itself.
• internal/core/analyzer: CTEs, set operations, subqueries in FROM and as expressions (including correlated ones), functions in FROM, IN, BETWEEN, CASE, COALESCE, array expressions, casts, and output-name references in GROUP BY/HAVING. Overloads are chosen by argument type, polymorphic return types (max(anyelement)) resolve to the argument's type, and an unknown function or operator leaves the expression untyped instead of failing the whole query.

Behavior change

analyze reports type names as the catalog stores them, in lower case — so SQLite's INTEGER is now integer. The analyze_basic/sqlite golden reflects that, and docs/howto/analyze.md calls it out.

Testing

Nine new end-to-end cases (analyze_select, analyze_dml, analyze_params for each of the three migrated dialects) cover joins, aggregates, CTEs, RETURNING, multi-table DELETE, and sqlc.arg/narg/slice.

As a wider check I ran sqlc analyze over every PostgreSQL/MySQL/SQLite schema+query pair in examples/ and internal/endtoend/testdata — 262 pairs, of which 253 pass. Roughly twelve of the remaining eighteen are intentionally-invalid fixtures (invalid_table_alias, sqlc_arg_invalid, relation_does_not_exist, MySQL files written with $1). The genuine gaps left are recursive CTEs, MySQL schema-qualified column references, SQLite virtual tables and table-valued functions (json_each), and one MySQL self-join that references a table by a name it aliased away.

TestReplay, TestParse and TestFormat pass. The TestValidSchema failures in my environment are pre-existing — no databases run there, and the count is identical on main.

---

Generated by Claude Code