Class QueryDialectAbstract

A SQL dialect MJ can read: the facts needed to tokenize, analyze, screen and write queries for one database, split into facets.

• Lexical: how text splits into tokens (quotes, strings, comments, placeholders).
• Grammar: statement-level facts (row caps, CTE rules, hints, write keywords).
• Writer: how to write SQL fragments (quoting, literals, limit clause, expressions).
• Types and Binding: type-name sets and driver binding, where a dialect has them.

A dialect MJ itself runs on is a SQLDialect, which adds DDL. A source MJ only reads (an External Data Source) needs just a QueryDialect. GetQueryDialect resolves the built-in dialects directly; a third-party dialect registers with the MJ class factory (@RegisterClass(QueryDialect, '<key>')) and resolves the same way.