You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like there are way too many keywords listed for tsql, a lot of which aren't actual reserved keywords. Cleaning up this list to only leave the actual reserved keywords (as documented in here) should take care of the problem with VALUE and ZONE.
However with TIMESTAMP, which is also a name of a data type, SQL Formatter is unable to distinguish when it's being used as a data type and when it's being used as plain identifier.
I close this, as I fixed the problem with ODBC keywords (by just throwing them all away), but the problem with TIMESTAMP really can't be fixed within the current architecture of SQL Formatter . My suggestion is simply to not use the dataTypeCase: "lower" option.
Input data
Which SQL and options did you provide as input?
with the following options
Expected Output
Actual Output
Note the incorrect casing of
VALUE
,timestamp
, andZONE
.Usage
prettier-plugin-sql
tsql
master
branchThe text was updated successfully, but these errors were encountered: