SQL dialects draft reads

There is one parser, and it is deliberately tolerant rather than dialect-specific: it recognises the shapes CREATE TABLE takes in practice and steps over everything else without complaining. Each page below is generated by running the shipped tool over the fixture shown on it.

• PostgreSQLpg_dump output, ALTER TABLE keys
• MySQLmysqldump, backticks, inline keys
• SQLite.schema output, typeless columns
• SQL Serverbracketed names, clustered keys
• Snowflakethree-part names, transient tables

Anything else

A dialect with no page here is not a dialect that fails. The parser reads CREATE TABLE, column definitions, inline and table-level key constraints, and ALTER TABLE … ADD CONSTRAINT; it skips statements it does not recognise rather than refusing the file. If yours does not come out right, open an issue with the DDL.