Alan Cruickshank

Ah - so this is an issue where it's parsing the `1` as a numeric literal and then saying that it's not allowed as an identifier. To solve this we'd...

Hi @Ofir-Purple - I think I know what might be going on here. Would you mind running `sqlfluff parse` on the file in question and pasting the results here? I...

Just triaging this and yet, the `FOR JSON` syntax hasn't yet been implemented in our `TSQL` grammar. Docs here: https://docs.microsoft.com/en-us/sql/relational-databases/json/format-query-results-as-json-with-for-json-sql-server?view=sql-server-ver16

This sounds like a sensible default rather than needing to be something which is explicitly configurable. To set this up, you'd need to edit the `dialect_snowflake.py` file and add some...

I think this should be covered with `L003` - have you got an example of a query which isn't effectively fixed by that rule?

Yep - prototype of this work is on #3942 . Will be at least a week until that's ready to merge. Probably a few weeks until release. 🙏

I'm supportive of integrating sqlfluff with semgrep. We're already part of [megalinter](https://github.com/oxsecurity/megalinter/blob/main/docs/descriptors/sql_sqlfluff.md). If you're willing to put together the PR, I'm happy to take a look. One issue to be...

Running on the current master branch I can't recreate this issue. With the following file `test_big.sql`: ```sql SELECT some_long_filename ``` And the following `.sqlfluff` file: ```ini [sqlfluff] large_file_skip_char_limit = 10...

Very likely @fmms . @kieronellis - I would suggest using `large_file_skip_byte_limit` rather than `large_file_skip_char_limit` and upgrading to `1.3.1` which has much more robust support for both. Can you confirm whether...

I think this is well diagnosed. More specifically if I look at the grammar, I _think_ we should swap a `Ref("FunctionSegment")` for a `Ref("BaseExpressionElementGrammar")` at the beginning of `PivotClauseSegment`. `BaseExpressionElementGrammar`...