0.19.0

Parser upgrade

• Upgrade to sql-parser-cst 0.39.0

Other changes

• Switch to TypeScript 5.x

0.18.0

New feature

• The SQL code inside CREATE FUNCTION and CREATE PROCEDURE bodies now gets formatted. (#61) Thanks to @joelmukuthu
  This only applies when LANGUAGE sql is used in PostgreSQL.

0.17.4

Parser upgrade

• Upgrade to sql-parser-cst 0.38.2

0.17.3

Parser upgrade

• Upgrade to sql-parser-cst 0.38.1

0.17.2

sqlTypeCase option improvement

• ARRAY[] case is now effected in BigQuery by sqlTypeCase option, but not in PostgreSQL.
• Upgrade to sql-parser-cst 0.37.2

0.17.1

Parser update

• Upgrade to sql-parser-cst 0.37.1

0.17.0

New features

• Added sqlTypeCase option. (#13)
• Added sqlIdentifierCase option. (#13)
• Added sqlFunctionCase option. (#13)

Breaking changes

• PostgreSQL builtin data type names are now formatted in upper case by default.
  While all other (custom) data types are treated as identifiers and left as-is by default.
  Recommended setting for PostgreSQL is sqlTypeCase: "lower", sqlIdentifierCase: "lower".
  This way all data types in PostgreSQL get formatted in uniform way.

Improvements and bugfixes

• Improve formatting of DROP TABLE table1, table2, ... #58
• Improve formatting of ANALYZE TABLE table1, table2, ...
• Improve formatting of CREATE TABLE ... LIKE
• Ensure CREATE PROCEDURE is formatted similarly to CREATE FUNCTION

0.16.0

Change in formatting

• ADD CONSTRAINT in ALTER TABLE is now formatted like CONSTRAINT definitions in CREATE TABLE statement.

Before:

ALTER TABLE my_awesome_table
ADD CONSTRAINT some_constraint_name CHECK (
  my_awesome_table.column1 > my_awesome_table.column2
);

After:

ALTER TABLE my_awesome_table
ADD CONSTRAINT some_constraint_name
  CHECK (my_awesome_table.column1 > my_awesome_table.column2);

Other

• PostgreSQL parsing improvements from sql-parser-cst 0.36.1.

0.15.0

Breaking changes

• PostgreSQL data types are now treated as identifiers not keywords. So sqlKeywordCase option has no effect on these. In other dialects data types remain treated as keywords for now, but expect this to change in the future.

Improvements

• Imroved PostgreSQL data types support added by sql-parser-cst 0.36.0:
  • SETOF types
  • schema-qualified type names

0.14.2

Parser update

• Upgrade to sql-parser-cst 0.35.1