Rene Saarsoo

PS. Just FYI, when reporting bugs to this or any other open-source project, please don't answer "latest" when asked which version number you're using. That "latest" will no more be...

It's a very reasonable feature request. Unfortunately this is very unlikely to get implemented in SQL Formatter, because I'm not really doing any real feature development in this library. Rather...

Hard to say. Currently the main priority is to get PostgreSQL supported. Then MySQL/MariaDB. Given that SQL Server is proprietary, it's also harder implement support for it. Like with PostgreSQL...

Well, according to the documentation (and my testing) MariaDB supports `/* */` comments just fine. https://mariadb.com/docs/server/reference/sql-statements/comment-syntax

I'm not really sure I understand how you expect this to work. It would be better if you gave an example. Like how does SQL Formatter print GO right now...

OK. Thanks. Basically should format `GO` on separate line (like now) and add an additional line break after it.

See this issue for a workaround: https://github.com/sql-formatter-org/sql-formatter/issues/861

Thanks for reporting. Although this error occurs with other dialects, it's more of a PostgreSQL-specific issue as most SQL dialects don't allow reserved keywords to be used as aliases. PostgreSQL...

Thanks for reporting. Could you point me to Spark documentation for this syntax?

Thanks for the info. Looks like this is similar to [BigQuery STRUCT syntax](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#struct_type), except that in BigQuery doesn't support the colon. `ARRAY` is the same as in BigQuery, and then...