gudusoft.gsqlparser.pp2.dialect

Interface DialectStrategy

All Known Implementing Classes:

Db2Dialect, GenericDialect, MssqlDialect, MysqlDialect, OracleDialect, SnowflakeDialect

public interface DialectStrategy

Per-dialect layout behaviour. The lexical island pipeline consults the strategy for the (small) set of things that genuinely vary by vendor, instead of branching on EDbVendor throughout the rules. The DialectRegistry maps a vendor to its strategy (GenericDialect by default).

v2 keeps this surface deliberately small. New per-dialect behaviour is added only when a smoke test demands it (plan §7.5 #15); most dialects use GenericDialect.

Plan reference: §7.3/S30, §7.4/S30, §6 dialect/*.

Method Summary

Modifier and Type	Method and Description
Set<String>	additionalClauseKeywords() Upper-cased clause-start phrases for this dialect, beyond the universal clause keywords (FROM/WHERE/GROUP/ORDER/HAVING/...).
EDbVendor	getVendor() The vendor this strategy serves.

Method Detail

getVendor

EDbVendor getVendor()

The vendor this strategy serves.

additionalClauseKeywords

Set<String> additionalClauseKeywords()

Upper-cased clause-start phrases for this dialect, beyond the universal clause keywords (FROM/WHERE/GROUP/ORDER/HAVING/...). Each entry is one or more space-separated words; the clause-linebreak rule breaks before a phrase only when the whole phrase matches consecutive tokens (so "CONNECT BY" breaks before CONNECT, but a bare CONNECT does not). For example Oracle adds "CONNECT BY" / "START WITH" and Snowflake adds "QUALIFY". GenericDialect returns an empty set.