0.39.0

Breaking changes

• Support multiple names in DROP PROCEDURE & DROP FUNCTION (02cb895, cbd0e15)
• Use FunctionSignature type in AlterProcedureStmt & AlterFunctionStmt (ebeae15, 88d220d)
• Rename DropFunctionStmt.functions to .signatures (eac1972)
• Don't recognize paren-less functions as plain function calls (15ada0f)

Other changes

• Upgrade to TypeScript 5.x
• Support SET as column name (but not as implicit alias)
• Support interval units (year, month, ...) as column names

0.38.2

Bugfix

• Fix interval expression parsing (#60)

0.38.1

Fix regression in previous release

• Allow any expression in IntervalLiteral.value

0.38.0

Breaking changes to intervals parsing

• Instead of parsing interval literals in PostgreSQL as IntervalLiteral and in other dialects as IntervalExpr, they are now always parsed as IntervalLiteral (175465f)
• IntervalDataType properties fieldsKw and precision have been replaced with unit: IntervalUnit | IntervalUnitRange, making it more similar to IntervalLiteral (fc3f9e6)
• Move IntervalUnit and IntervalUnitRange types have been moved from AllExprNodes to AllDataTypeNodes (2ae45dc)

Improved PostgreSQL intervals support

• Support INTERVAL '15' SECOND (precision) literal syntax
• Support INTERVAL (precision) '25' literal syntax

0.37.2

ARRAY[] is now parsed differently in BigQuery and PostgreSQL. #127

• in BigQuery it's parsed as typed_expr as before.
• in PostgreSQL it's now parsed as array_literal_expr.

0.37.1

New feature

Conditional comments to disable the parser for sections of SQL (#125)

SELECT * FROM foo;
/* sql-parser-cst-disable */
SOME PROBLEMATIC SQL;
/* sql-parser-cst-enable */
CREATE TABLE tbl (pos float8_range NOT NULL);

0.37.0

Breaking changes

Major changes to how data types are parsed:

• named_data_type is now replaced with data_type_name and modified_data_type (309399d, 1605b6d)
• INTERVAL types are now parsed as interval_data_type (fd1470d, b349053)
• with_time_zone_data_type is now replaced with time_data_type (df42f4a, 5c3e587)
• BigQuery parametric types are now parsed as parametric_data_type (3bc4388)
• PostgreSQL builtin data type names are now parsed as keywords inside data_type_name. data_type_identifier node no more exists.
• Other PostgreSQL data type names are parsed as identifiers.

Other changes

• PostgreSQL NATIONAL CHAR data types are now supported.

0.36.1

Improved PostgreSQL support

• Proper PostgreSQL operators support. Now recognizing any possibly operator instead of just a predefined list of the most well-known operators (#122, #79)
• Support identifiers in PostgreSQL type modifiers, like GEOMETRY(POINT, 123) (#121)

0.36.0

Breaking changes

• PostgreSQL data types are now parsed as identifiers (not keywords).
• PostgreSQL data type names are now wrapped in data_type_identifier node.

Improved PostgreSQL data types support

• Support schema-qualified type names #120
• Support SETOF types #120

0.35.1

Bugfix

• Add missing INTERVAL units for BigQuery #119