-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure on schema-qualified special OPERATOR
in PostgreSQL
#711
Comments
OPERATOR
in PostgresQLOPERATOR
in PostgreSQL
Thanks for reporting. That's definitely a tricky bit of syntax to handle. You might be interested in trying out prettier-plugin-sql-cst. It doesn't yet have a full PostgreSQL support, but it does handle the I can thing of several hacks to fix this issue in sql-formatter. Will have to figure out which one would be the least hacky way of doing it. |
Thanks; I am following that project and plan to switch to it when its Postgres support matures more, but for now here we are 🙂 |
If you know of anything particular that's missing from the current PostgreSQL support in the |
FYI, in case anyone else is having similar issues, I also discovered I gave |
+1 on the |
There's actually a workaround for the paramTypes: {
custom: [{ regex: String.raw`OPERATOR *\([^)]+\)` }]
} However with regards to |
Well... as I'm looking into this already, might as well fix it... |
Describe the bug
Expected behavior
Useful output
Actual behavior
Failure
Usage
Yeah, this syntax is weird; unfortunately, it's generated by
pg_dump
in some cases, so my scripts that pipe schema dump throughsql-formatter
are failing.The text was updated successfully, but these errors were encountered: