Rene Saarsoo

Closing this as it's a duplicate of a very old feature request: #329

Just FYI. I'm open to pull requests, but I'm unlikely to implement this by myself.

Thanks for reporting. You're right in your diagnosis that the formatter thinks that this is a WITH-clause. Unfortunately this problem is pretty tricky to solve with the current architecture of...

Thanks for reporting. The `acceptUnsupportedGrammar` doesn't really work well. It was a quick hack I did, which unfortunately only works when there's some totally unsupported SQL statement like `CREATE SPELL...

Thanks for reporting, but unfortunately the support for procedural SQL in SQL-Formatter is pretty much non-existant, and it's unlikely to be supported in any foreseeable future because it's not really...

Fixed in [15.6.10](https://github.com/sql-formatter-org/sql-formatter/releases/tag/v15.6.10)

Yes, `{language: "transactsql"}` is the correct setting to use for SQL Server. I have no idea what this `{d'2024-01` syntax is. Please provide a full code example.

So, the problem is with this `{d'2024-01-01'}` syntax. What is this? Is it something that SQL Server supports natively or is it something else? It would be great if you...

I think a simple fix would be to just treat `{...}` as strings. That should be easily to do by just adding `'{}'` to `stringTypes` array: https://github.com/sql-formatter-org/sql-formatter/blob/master/src/languages/transactsql/transactsql.formatter.ts#L249 Unless there's some...

Configure the [paramTypes](https://github.com/sql-formatter-org/sql-formatter/blob/master/docs/paramTypes.md) option to recognize `:name` parameters: ``` paramTypes: { named: [':'] }, ```