Package: simple-ddl-parser
Simple DDL ParserBuild with ply (lex & yacc in python). A lot of samples in ‘tests/.Is it Stable?Yes, library already has about 9000+ downloads per day  -https://pypistats.org/packages/simple-ddl-parser..As maintainer, I guarantee that any backward incompatible changes will not be done in patch or minor version. But! Pay attention that sometimes output in keywords can be changed in minor version because of fixing wrong behaviour in past.Updates in version 1.xThe full list of updates can be found in the Changelog below (at the end of README).Version 1.0.0 was released due to significant changes in the output structure and a stricter approach regarding the scope of the produced output. Now, you must provide the argument ‘output_mode=name_of_your_dialect’ if you wish to see arguments/properties specific to a particular dialectHow does it work?Parser supports:SQLHQL (Hive)MSSQL dialecOracle dialectMySQL dialectPostgreSQL dialectBigQueryRedshiftSnowflakeSparkSQLIBM DB2 dialectYou can check dialects sections afterSupported Statementssection to get more information that statements from dialects already supported by parser. If you need to add more statements or new dialects - feel free to open the issue.Feel free to open Issue with DDL samplePay attentions that I’m adding functional tests for all supported statement, so if you see that your statement is failed and you didn’t see it in the test 99,9% that I did n’t have sample with such SQL statement - so feel free to open the issue and I will add support for it.If you need some statement, that not supported by parser yet: please provide DDL example & information about that is it SQL dialect or DB.Types that are used in your DB does not matter, so parser must also work successfully to any DDL for SQL DB. Parser is NOT case sensitive, it did not expect that all queries will be in upper case or lower case. So you can write statements like this:AlterTablePersonsADDCONSTRAINTCHK_PersonAgeCHECK(Age>=18ANDCity='Sandnes');It will be parsed as is without errors.If you have samples that cause an error - please open the issue (but don’t forget to add ddl example), I will be glad to fix it.A lot of statements and output result you can find in tests on the github -https://github.com/xnuinside/simple-ddl-parser/tree/main/tests.How to installpipinstallsimple-ddl-parserHow to useExtract additional information from HQL (& other dialects)In some dialects like HQL there is a lot of additional information about table like, fore example, is it external table, STORED AS, location & etc. This property will be always empty in ‘classic’ SQL DB like PostgreSQL or MySQL and this is the reason, why by default this information are ‘hidden’.
Also some fields hidden in HQL, because they are simple not exists in HIVE, for example ‘deferrable_initially’
To get this ‘hql’ specific details about table in output please use ‘output_mode’ argument in run() method.example:ddl="""
CREATE TABLE IF NOT EXISTS default.salesorderdetail(
    SalesOrderID int,
    ProductID int,
    OrderQty int,
    LineTotal decimal
    )
PARTITIONED BY (batch_id int, batch_id2 string, batch_32 some_type)
LOCATION 's3://datalake/table_name/v1'
ROW FORMAT DELIMITED
    FIELDS TERMINATED BY ','
    COLLECTION ITEMS TERMINATED BY '\002'
    MAP KEYS TERMINATED BY '\003'
STORED AS TEXTFILE
"""result=DDLParser(ddl).run(output_mode="hql")print(result)And you will get output with additional keys ‘stored_as’, ‘location’, ‘external’, etc.# additional keys examples{...,'location':"'s3://datalake/table_name/v1'",'map_keys_terminated_by':"'\\003'",'partitioned_by':[{'name':'batch_id','size':None,'type':'int'},{'name':'batch_id2','size':None,'type':'string'},{'name':'batch_32','size':None,'type':'some_type'}],'primary_key':[],'row_format':'DELIMITED','schema':'default','stored_as':'TEXTFILE',...}If you run parser with command line add flag ‘-o=hql’ or ‘–output-mode=hql’ to get the same result.Possible output_modes: [‘redshift’, ‘spark_sql’, ‘mysql’, ‘bigquery’, ‘mssql’, ‘databricks’, ‘sqlite’, ‘vertics’, ‘ibm_db2’, ‘postgres’, ‘oracle’, ‘hql’, ‘snowflake’, ‘sql’]From python codefromsimple_ddl_parserimportDDLParserparse_results=DDLParser("""create table dev.data_sync_history(
    data_sync_id bigint not null,
    sync_count bigint not null,
    sync_mark timestamp  not  null,
    sync_start timestamp  not null,
    sync_end timestamp  not null,
    message varchar(2000) null,
    primary key (data_sync_id, sync_start)
); """).run()print(parse_results)To parse from filefromsimple_ddl_parserimportparse_from_fileresult=parse_from_file('tests/sql/test_one_statement.sql')print(result)From command linesimple-ddl-parser is installed to environment as commandsdpsdppath_to_ddl_file# for example:sdptests/sql/test_two_tables.sqlYou will see the output inschemasfolder in file with nametest_two_tables_schema.jsonIf you want to have also output in console - use-vflag for verbose.sdptests/sql/test_two_tables.sql-vIf you don’t want to dump schema in file and just print result to the console, use–no-dumpflag:sdptests/sql/test_two_tables.sql--no-dumpYou can provide target path where you want to dump result with argument-t,–target:sdptests/sql/test_two_tables.sql-tdump_results/Get Output in JSONIf you want to get output in JSON in stdout you can use argumentjson_dump=Truein method.run()for thisfromsimple_ddl_parserimportDDLParserparse_results=DDLParser("""create table dev.data_sync_history(
    data_sync_id bigint not null,
    sync_count bigint not null,
); """).run(json_dump=True)print(parse_results)Output will be:[{"columns":[{"name":"data_sync_id","type":"bigint","size":null,"references":null,"unique":false,"nullable":false,"default":null,"check":null},{"name":"sync_count","type":"bigint","size":null,"references":null,"unique":false,"nullable":false,"default":null,"check":null}],"primary_key":[],"alter":{},"checks":[],"index":[],"partitioned_by":[],"tablespace":null,"schema":"dev","table_name":"data_sync_history"}]More detailsDDLParser(ddl).run().run() method contains several arguments, that impact changing output result. As you can saw upper exists argumentoutput_modethat allow you to set dialect and get more fields in output relative to chosen dialect, for example ‘hql’. Possible output_modes: [‘redshift’, ‘spark_sql’, ‘mysql’, ‘bigquery’, ‘mssql’, ‘databricks’, ‘sqlite’, ‘vertics’, ‘ibm_db2’, ‘postgres’, ‘oracle’, ‘hql’, ‘snowflake’, ‘sql’]Also in .run() method exists argumentgroup_by_type(by default: False). By default output of parser looks like a List with Dicts where each dict == one entity from ddl (table, sequence, type, etc). And to understand that is current entity you need to check Dict like: if ‘table_name’ in dict - this is a table, if ‘type_name’ - this is a type & etc.To make work little bit easy you can set group_by_type=True and you will get output already sorted by types, like:{'tables':[all_pasrsed_tables],'sequences':[all_pasrsed_sequences],'types':[all_pasrsed_types],'domains':[all_pasrsed_domains],...}For example:ddl="""
CREATE TYPE "schema--notification"."ContentType" AS
    ENUM ('TEXT','MARKDOWN','HTML');
    CREATE TABLE "schema--notification"."notification" (
        content_type "schema--notification"."ContentType"
    );
CREATE SEQUENCE dev.incremental_ids
    INCREMENT 10
    START 0
    MINVALUE 0
    MAXVALUE 9223372036854775807
    CACHE 1;
"""result=DDLParser(ddl).run(group_by_type=True)# result will be:{'sequences':[{'cache':1,'increment':10,'maxvalue':9223372036854775807,'minvalue':0,'schema':'dev','sequence_name':'incremental_ids','start':0}],'tables':[{'alter':{},'checks':[],'columns':[{'check':None,'default':None,'name':'content_type','nullable':True,'references':None,'size':None,'type':'"schema--notification"."ContentType"','unique':False}],'index':[],'partitioned_by':[],'primary_key':[],'schema':'"schema--notification"','table_name':'"notification"'}],'types':[{'base_type':'ENUM','properties':{'values':["'TEXT'","'MARKDOWN'","'HTML'"]},'schema':'"schema--notification"','type_name':'"ContentType"'}]}ALTER statementsRight now added support only for ALTER statements with FOREIGEIN keyFor example, if in your ddl after table definitions (create table statements) you have ALTER table statements like this:ALTERTABLE"material_attachments"ADDFOREIGNKEY("material_id","material_title")REFERENCES"materials"("id","title");This statements will be parsed and information about them putted inside ‘alter’ key in table’s dict.
For example, please check alter statement tests -tests/test_alter_statements.pyMore examples & testsYou can find intests/folder.Dump result in jsonTo dump result in json use argument .run(dump=True)You also can provide a path where you want to have a dumps with schema with argument .run(dump_path=’folder_that_use_for_dumps/’)Raise error if DDL cannot be parsed by ParserBy default Parser does not raise the error if some statement cannot be parsed - and just skip & produce empty output.To change this behavior you can pass ‘silent=False’ argumen to main parser class, like:DDLParser(.., silent=False)Normalize namesUse DDLParser(.., normalize_names=True)flag that change output of parser:
If flag is True (default ‘False’) then all identifiers will be returned without ‘[’, ‘”’ and other delimiters that used in different SQL dialects to separate custom names from reserved words & statements.
For example, if flag set ‘True’ and you pass this input:CREATE TABLE [dbo].TO_RequestsNOT NULL,[user_id] [int]In output you will have names like ‘dbo’ and ‘TO_Requests’, not ‘[dbo]’ and ‘[TO_Requests]’.Supported StatementsCREATE [OR REPLACE] TABLE [ IF NOT EXISTS ] + columns definition, columns attributes: column name + type + type size(for example, varchar(255)), UNIQUE, PRIMARY KEY, DEFAULT, CHECK, NULL/NOT NULL, REFERENCES, ON DELETE, ON UPDATE,  NOT DEFERRABLE, DEFERRABLE INITIALLY, GENERATED ALWAYS, STORED, COLLATESTATEMENTS: PRIMARY KEY, CHECK, FOREIGN KEY in table definitions (in create table();)ALTER TABLE STATEMENTS: ADD CHECK (with CONSTRAINT), ADD FOREIGN KEY (with CONSTRAINT), ADD UNIQUE, ADD DEFAULT FOR, ALTER TABLE ONLY, ALTER TABLE IF EXISTS; ALTER .. PRIMARY KEY; ALTER .. USING INDEX TABLESPACE; ALTER .. ADD; ALTER .. MODIFY; ALTER .. ALTER COLUMN; etcPARTITION BY statementCREATE SEQUENCE with words: INCREMENT [BY], START [WITH], MINVALUE, MAXVALUE, CACHECREATE TYPE statement:  AS TABLE, AS ENUM, AS OBJECT, INTERNALLENGTH, INPUT, OUTPUTLIKE statement (in this and only in this case to output will be added ‘like’ keyword with information about table from that we did like - ‘like’: {‘schema’: None, ‘table_name’: ‘Old_Users’}).TABLESPACE statementCOMMENT ON statementCREATE SCHEMA [IF NOT EXISTS] … [AUTHORIZATION] …CREATE DOMAIN [AS]CREATE [SMALLFILE | BIGFILE] [TEMPORARY] TABLESPACE statementCREATE DATABASE + Properties parsingSparkSQL Dialect statementsUSINGHQL Dialect statementsPARTITIONED BY statementROW FORMAT, ROW FORMAT SERDEWITH SERDEPROPERTIES (“input.regex” =  “..some regex..”)STORED AS (AVRO, PARQUET, etc), STORED AS INPUTFORMAT, OUTPUTFORMATCOMMENTLOCATIONFIELDS TERMINATED BY, LINES TERMINATED BY, COLLECTION ITEMS TERMINATED BY, MAP KEYS TERMINATED BYTBLPROPERTIES (‘parquet.compression’=’SNAPPY’ & etc.)SKEWED BYCLUSTERED BYMySQLON UPDATE in column without referenceMSSQLCONSTRAINT [CLUSTERED]… PRIMARY KEYCONSTRAINT … WITH statementPERIOD FOR SYSTEM_TIME in CREATE TABLE statementON [PRIMARY] after CREATE TABLE statement (sample in test files test_mssql_specific.py)WITH statement for TABLE propertiesTEXTIMAGE_ON statementDEFAULT NEXT VALUE FOR in COLUMN DEFAULTMSSQL / MySQL/ Oracletype IDENTITY statementFOREIGN KEY REFERENCES statement‘max’ specifier in column sizeCONSTRAINT … UNIQUE, CONSTRAINT … CHECK, CONSTRAINT … FOREIGN KEY, CONSTRAINT … PRIMARY KEYCREATE CLUSTERED INDEXCREATE TABLE (…) ORGANIZATION INDEXOracleENCRYPT column property [+ NO SALT, SALT, USING]STORAGE column propertyPotgreSQLINHERITS table statement -https://postgrespro.ru/docs/postgresql/14/ddl-inheritAWS Redshift Dialect statementsENCODE column propertySORTKEY, DISTSTYLE, DISTKEY, ENCODE table propertiesCREATE TEMP / TEMPORARY TABLEsyntax like with LIKE statement:create temp table tempevent(like event);Snowflake Dialect statementsCREATE .. CLONE statements for table, database and schemaCREATE TABLE [or REPLACE] [ TRANSIENT | TEMPORARY ] .. CLUSTER BY ..CONSTRAINT .. [NOT] ENFORCEDCOMMENT = in CREATE TABLE & CREATE SCHEMA statementsWITH MASKING POLICYWITH TAG, including multiple tags in the same statement.DATA_RETENTION_TIME_IN_DAYSMAX_DATA_EXTENSION_TIME_IN_DAYSCHANGE_TRACKINGBigQueryOPTION in CREATE SCHEMA statementOPTION in CREATE TABLE statementOPTION in column definition statementParser settingsLoggingLogging to fileTo get logging output to file you should provide to Parser ‘log_file’ argument with path or file name:DDLParser(ddl, log_file='parser221.log').run(group_by_type=True)Logging levelTo set logging level you should provide argument ‘log_level’DDLParser(ddl, log_level=logging.INFO).run(group_by_type=True)Thanks for involving & contributionsMost biggest ‘Thanks’ ever goes for contributions in parser:https://github.com/dmaresmahttps://github.com/cfhoweshttps://github.com/swiatek25https://github.com/slurpybhttps://github.com/PBalsdonBig thanks for the involving & contribution with test cases with DDL samples & opening issues goes to:https://github.com/kukigai,https://github.com/Awalkman90,https://github.com/geob3dfor help with debugging & testing support for BigQuery dialect DDLs:https://github.com/ankitdata,https://github.com/kalyan939Changelogv1.0.3ImprovementsFixed bug withCREATE OR REPLACE SCHEMA.Added support of create empty tables without columns CREATE TABLE tablename (); (valid syntax in SQL)SnowflakeFixed bug with snowflakestage_fileformat option value equal a single string asFIELD_OPTIONALLY_ENCLOSED_BY ='\"',FIELD_DELIMITER = '|'improve snowflake fileformat key equals value into dict. type.v1.0.2ImprovementsFixed bug with places first table property value in ‘authorization’ key. Now it is used real property name.Fixed typo on Databricks dialectimproved equals symbols support within COMMENT statement.turn regexp into functionsMySQL ImprovementsUNSIGNED property after int parsed validly nowSnowflakeSnowflake TAG now available on SCHEMA definitions.v1.0.1Minor FixesWhen usingnormalize_names=Truedo not remove[]from types likedecimal(21)[].When usingnormalize_names=Trueensure that"complex"."type"style names convert tocomplex.type.v1.0.0In output structure was done important changes that can in theory breaks code.Important changesImportant change:all custom table properties that are defined after column definition in ‘CREATE TABLE’ statement and relative to only one dialect (only for SparkSQL, or HQL,etc), for example, like here:https://github.com/xnuinside/simple-ddl-parser/blob/main/tests/dialects/test_snowflake.py#L767orhttps://github.com/xnuinside/simple-ddl-parser/blob/main/tests/dialects/test_spark_sql.py#L133will be saved now in propertytable_propertiesas dict.
Previously they was placed on same level of table output ascolumns,alter, etc. Now, they grouped and moved to keytable_properties.Formatting parser result now represented by 2 classes - Output & TableData, that makes it more strict and readable.The output mode now functions more strictly. If you want to obtain output fields specific to a certain dialect,
use output_mode=’snowflake’ for Snowflake or output_mode=’hql’ for HQL, etc.
Previously, some keys appeared in the result without being filtered by dialect.
For example, if ‘CLUSTER BY’ was in the DDL, it would show up in the ‘cluster_by’ field regardless of the output mode.
However, now all fields that only work in certain dialects and are not part of the basic SQL notation will only be shown
if you choose the correct output_mode.New Dialects supportAdded as possible output_modes new Dialects:Databricks SQL like ‘databricks’,Vertica as ‘vertica’,SqliteFields as ‘sqlite’,PostgreSQL as ‘postgres’Full list of supported dialects you can find in dict -supported_dialects:from simple_ddl_parser import supported_dialectsCurrently supported: [‘redshift’, ‘spark_sql’, ‘mysql’, ‘bigquery’, ‘mssql’, ‘databricks’, ‘sqlite’, ‘vertics’, ‘ibm_db2’, ‘postgres’, ‘oracle’, ‘hql’, ‘snowflake’, ‘sql’]If you don’t see dialect that you want to use - open issue with description and links to Database docs or use one of existed dialects.Snowflake updates:For some reasons, ‘CLONE’ statement in SNOWFLAKE was parsed into ‘like’ key in output. Now it was changed to ‘clone’ - inner structure of output stay the same as previously.MySQL updates:Engine statement now parsed correctly. Previously, output was always ‘=’.BigQuery updates:Word ‘schema’ totally removed from output.Datasetused instead ofschemain BigQuery dialect.v0.32.1Minor FixesRemoved debug printv0.32.0ImprovementsAdded support for several ALTER statements (ADD, DROP, RENAME, etc) -https://github.com/xnuinside/simple-ddl-parser/issues/215In ‘alter’ output added several keys:‘dropped_columns’ - to store information about columns that was in table, but after dropped by alter‘renamed_columns’ - to store information about columns that was renamed‘modified_columns’ - to track alter column changes for defaults, datetype, etc. Argument stores previous columns states.FixesInclude source column names in FOREIGN KEY references. Fix for:https://github.com/xnuinside/simple-ddl-parser/issues/196ALTER statement now will be parsed correctly if names & schemas written differently increate tablestatement and alter.
For example, if in create table you use quotes like “schema_name”.”table_name”, but in alter was schema_name.table_name - previously it didn’t work, but now parser understand that it is the same table.v0.31.3ImprovementsSnowflake update:Added support for Snowflake Virtual Column definition in External ColumnAS ()statement -https://github.com/xnuinside/simple-ddl-parser/issues/218enforce support for Snowflake _FILE_FORMAT options in External Column ddl statement -https://github.com/xnuinside/simple-ddl-parser/issues/221OthersSupport for KEY statement in CREATE TABLE statements. KEY statements will now create INDEX entries in the DDL parser.v0.31.2ImprovementsSnowflake update:Added support for Snowflake AUTOINCREMENT | IDENTITY column definitions with optional parameterORDER|NOORDERstatement -https://github.com/xnuinside/simple-ddl-parser/issues/213CommonAdded param ‘encoding’ to parse_from_file function -https://github.com/xnuinside/simple-ddl-parser/issues/142.
Default encoding is utf-8.v0.31.1ImprovementsSnowflake update:Support multiple tag definitions in a singleWITH TAGstatement.Added support for Snowflake double single quotes -https://github.com/xnuinside/simple-ddl-parser/issues/208v0.31.0Fixes:Move inline flag in regexp (issue with python 3.11) -https://github.com/xnuinside/simple-ddl-parser/pull/200Fix for:https://github.com/xnuinside/simple-ddl-parser/issues/199Improvements:AddedSnowflake Table DDL support of WITH MASKING POLICY column definition-https://github.com/xnuinside/simple-ddl-parser/issues/201Updates:All deps updated to the latest versions.v0.30.0Fixes:IDENTITY now parsed normally as a separate column property. Issue:https://github.com/xnuinside/simple-ddl-parser/issues/184New Features:IN TABLESPACE IBM DB2 statement now is parsed into ‘tablespace’ key. Issue:https://github.com/xnuinside/simple-ddl-parser/issues/194.
INDEX IN also parsed to ‘index_in’ key.
Added support for ORGANIZE BY statementAdded support for PostgreSQL INHERITS statement. Issue:https://github.com/xnuinside/simple-ddl-parser/issues/191v0.29.1Important updates:Python 3.6 is deprecated in tests and by default, try to move to Python3.7, but better to 3.8, because 3.7 will be deprecated in 2023.FixesFix forhttps://github.com/xnuinside/simple-ddl-parser/issues/177ImprovementsAdded support for Oracle 2 component size for types, like ‘30 CHAR’. Fromhttps://github.com/xnuinside/simple-ddl-parser/issues/176v0.29.0FixesAUTOINCREMENT statement now parsed validly same way as AUTO_INCREMENT and showed up in output as ‘autoincrement’ property of the column
Fix for:https://github.com/xnuinside/simple-ddl-parser/issues/170Fix issue ‘ TypeError argument of type ‘NoneType’ is not iterable’ on some foreigen keyshttps://github.com/xnuinside/simple-ddl-parser/issues/148New FeaturesSupport for non-numeric column type parametershttps://github.com/xnuinside/simple-ddl-parser/issues/171It shows in column attribute ‘type_parameters’.v0.28.1Improvements:Lines started with INSERT INTO statement now successfully ignored by parser (so you can keep them in ddl - they will be just skipped)Fixes:Important fix for multiline commentsv0.28.0Important Changes (Pay attention):Because of parsing now AUTO_INCREMENT as a separate property of column previous output changed.
Previously it was parsed as a part of type like:  ‘INT AUTO_INCREMENT’.
Now type will be only ‘INT’, but in column property you will see ‘autoincrement’: True.Amazing innovation:It’s is weird to write in Changelog, but only in version 0.28.0 I recognize that floats that not supported by parser & it was fixed.
Thanks for the sample in the issue:https://github.com/xnuinside/simple-ddl-parser/issues/163Improvements:
MariaDB:Added support for MariaDB AUTO_INCREMENT (from ddl here -https://github.com/xnuinside/simple-ddl-parser/issues/144)
If column is Auto Incremented - it indicated as ‘autoincrement’: True in column definitionCommon:Added parsing for multiline comments in DDL with/* */syntax.Comments from DDL now all placed in ‘comments’ keyword if you usegroup_by_type=arg in parser.Added argument ‘parser_settings={}’ (dict type) in method  parse_from_file() - this way you can pass any arguments that you want to DDLParser (& that supported by it)
So, if you want to set log_level=logging.WARNING for parser - just use it as:
parse_from_file(‘path_to_file’, parser_settings={‘log_level’: logging.WARNING}). For issue:https://github.com/xnuinside/simple-ddl-parser/issues/160v0.27.0Fixes:Fixed parsing CHECKS with IN statement -https://github.com/xnuinside/simple-ddl-parser/issues/150@# symbols added to ID token - (partially)https://github.com/xnuinside/simple-ddl-parser/issues/146Improvements:Added support for ‘*’ in size column (ORACLE dialect) -https://github.com/xnuinside/simple-ddl-parser/issues/151Added arg ‘debug’ to parser, works same way as ‘silent’ - to get more clear error output.New features:Added support for ORACLE ‘ORGANIZATION INDEX’Added support for SparkSQL Partition by with procedure call -https://github.com/xnuinside/simple-ddl-parser/issues/154Added support for DEFAULT CHARSET statement MySQL -https://github.com/xnuinside/simple-ddl-parser/issues/153v0.26.5Fixes:Parsetab included in builds.Added additional argumen log_file=’path_to_file’, to enable logging to file with providen name.v0.26.4Bugfix for (support CREATE OR REPLACE with additional keys like transient/temporary):https://github.com/xnuinside/simple-ddl-parser/issues/133v0.26.3Improvements:Added support for OR REPLACE in CREATE TABLE:https://github.com/xnuinside/simple-ddl-parser/issues/131Added support for AUTO INCREMENT in column:https://github.com/xnuinside/simple-ddl-parser/issues/130v0.26.2Fixes:Fixed a huge bug for incorrect parsing lines with ‘USE’ & ‘GO’ strings inside.Fixed parsing for CREATE SCHEMA for Snowlake & Oracle DDLsImprovements:Added  COMMENT statement for CREATE TABLE ddl (for SNOWFLAKE dialect support)Added  COMMENT statement for CREATE SCHEMA ddl (for SNOWFLAKE dialect support)v0.26.1Fixes:support Multiple SERDEPROPERTIES  -https://github.com/xnuinside/simple-ddl-parser/issues/126Fix for issue with LOCATION and TBLPROPERTIES clauses in CREATE TABLE LIKE -https://github.com/xnuinside/simple-ddl-parser/issues/125LOCATION now works correctly with double quote stringsv0.26.0Improvements:Added more explicit debug message on Statement errors -https://github.com/xnuinside/simple-ddl-parser/issues/116Added support for “USING INDEX TABLESPACE” statement in ALTER -https://github.com/xnuinside/simple-ddl-parser/issues/119Added support for IN statements in CHECKS -https://github.com/xnuinside/simple-ddl-parser/issues/121New features:Support SparkSQL USING -https://github.com/xnuinside/simple-ddl-parser/issues/117Updates initiated by tickethttps://github.com/xnuinside/simple-ddl-parser/issues/120:In Parser you can use argument json_dump=True in method .run() if you want get result in JSON format.README updatedFixes:Added support for PARTITION BY one column without typeAlter table add constraint PRIMARY KEY -https://github.com/xnuinside/simple-ddl-parser/issues/119Fix for paring SET statement -https://github.com/xnuinside/simple-ddl-parser/pull/122Fix for disappeared columns without properties -https://github.com/xnuinside/simple-ddl-parser/issues/123v0.25.0Fixes:Fix for issue with ‘at time zone’https://github.com/xnuinside/simple-ddl-parser/issues/112New features:Added flag to raise errors if parser cannot parse statement DDLParser(.., silent=False) -https://github.com/xnuinside/simple-ddl-parser/issues/109Added flag to DDLParser(.., normalize_names=True) that change output of parser:
if flag is True (default ‘False’) then all identifiers will be returned without ‘[’, ‘”’ and other delimiters that used in different SQL dialects to separate custom names from reserved words & statements.
For example, if flag set ‘True’ and you pass this input:CREATE TABLE [dbo].TO_RequestsNOT NULL,[user_id] [int]In output you will have names like ‘dbo’ and ‘TO_Requests’, not ‘[dbo]’ and ‘[TO_Requests]’.v0.24.2Fixes:Fix for the issue:https://github.com/xnuinside/simple-ddl-parser/issues/108(reserved words can be used as table name after ‘.’)v0.24.1Fixes:HQL:fields_terminated_by now parses , as “’,’”, not as ‘’ previouslyCommon:To output added ‘if_not_exists’ field in result to get availability 1-to-1 re-create ddl by metadata.v0.24.0Fixes:HQL:More then 2 tblproperties now are parsed correctlyhttps://github.com/xnuinside/simple-ddl-parser/pull/104Common:‘set’ in lower case now also parsed validly.Now names like ‘schema’, ‘database’, ‘table’ can be used as names in CREATE DATABASE | SCHEMA | TABLESPACE | DOMAIN | TYPE statements and after INDEX and CONSTRAINT.Creation of empty tables also parsed correctly (like CREATE Table table;).New Statements Support:HQL:Added support for CLUSTERED BY -https://github.com/xnuinside/simple-ddl-parser/issues/103Added support for  INTO … BUCKETSCREATE REMOTE DATABASE | SCHEMAv0.23.0Big refactoring: less code complexity & increase code coverage. Radon added to pre-commit hooks.Fixes:Fix for issue with ALTER UNIQUE -https://github.com/xnuinside/simple-ddl-parser/issues/101New FeaturesSQL Comments string from DDL now parsed to “comments” key in output.PostgreSQL:Added support for ALTER TABLE ONLY | ALTER TABLE IF EXISTSv0.22.5Fixes:Fix for issue with ‘<’ -https://github.com/xnuinside/simple-ddl-parser/issues/89v0.22.4Fixes:BigQuery:Fixed issue with parsing schemas with project in name.Added support for multiple OPTION() statementsv0.22.3Fixes:BigQuery:CREATE TABLE statement with ‘project_id’ in format like project.dataset.table_name now is parsed validly.
‘project’ added to output.
Also added support project.dataset.name format in CREATE SCHEMA and ALTER statementv0.22.2Fixes:Fix for the issue:https://github.com/xnuinside/simple-ddl-parser/issues/94(column name starts with CREATE)v0.22.1New Features:BigQuery:Added support for OPTION for full CREATE TABLE statement & column definitionImprovements:CLUSTED BY can be used without ()