Releases: sql-formatter-org/sql-formatter
Releases · sql-formatter-org/sql-formatter
14.0.0
Breaking changes
These already deprecated features were fundamentally broken and have been removed for good:
- Removed
tabulateAlias
config option. - Removed
commaPosition
config option.
Potentially breaking:
- The DB2 support has been completely overhauled. Previously it was a mix of features from DB2 for IBM z mainframe and DB2 for LUW (Linux, Unix, Windows). Now the dialect named "db2" specifically targets the LUW variant.
- Snowflake dialect now includes all data types in the keywords list. Which means that when
keywordCase: upper
option is used, the data type names are also converted to uppercase. (#641) - The
SqlLanguage
type is no more just a plain string (a regression), but a union of the builtin SQL dialect names. - The
DialectOptions
type now includes a mandatoryname
field. (Relevant only when implementing a custom dialect.)
New features
- New experimental
identifierCase
config option. This works similarly to the existingkeywordCase
option. (Thanks to Christian Jorgensen.)
Bugfixes
- Various tweaks and fixes for the new DB2i dialect (introduced in 13.1.0).
- Fixed formatting of
TIMESTAMP() WITH TIME ZONE
in PostgreSQL (#618) - Improved error messages from the parser to help users self-diagnose the most common issues.
13.1.0
13.0.4
13.0.3
13.0.2
13.0.1
13.0.0
Breaking changes
- Reduced the keywords lists of MySQL, MariaDB and SingleStoreDB to just the reserved ones. #629
This means that usingkeywordCase: upper
no more capitalizes words likeuser
andname
. - Changed how
COMMENT
keyword is formatted. #636
In dialects like MariaDB (which allow it insideCREATE TABLE
statement) it is no more placed on a separate line.
In dialects which supportCOMMENT ON ...
statement, it only triggers a new line when used together withON
.