Alan Cruickshank
Alan Cruickshank
@robg-eb @nachimehta - I've made some progress on this with #5345, but I wasn't able to recreate exactly the error that you're getting. Can you share an example sql file...
PERFECT. That's exactly the test case I was looking for. Fix coming shortly.
@wojciech-mazur-mlg thanks for the bug report. I'll look into this.
@wojciech-mazur-mlg - could you try this with the most recent (3.2.0) SQLFluff release from this week. It updated the handling of some of these dbt issues. I've just tested a...
I've discussed with @mchen-codaio who's going to enable support for Snowflake and Trino.
@keraion - great feedback 👍 . On the `Count(*)` example and with explicit `ANTI` and `SEMI` joins I totally agree. I'll include some of those in the test cases. On...
> Could one or more of the maintainers run this rule on a large set of real-world queries? I do like the rule, but we may see surprise warnings from...
Update post maintainers call: I've removed the proposed config value, and now it only flags on explicit `LEFT`, `RIGHT` and `FULL` joins. I think this is otherwise ready for a...
@eirnym - I think this is already possible using the `configs` kwarg on `FluffConfig`. e.g. ```python configs = { "rules":{ "capitalisation.keywords": { "capitalisation_policy": "lower" } } } fluff_config = FluffConfig.from_kwargs(configs=configs)...
I've just checked this one - and it's already supported. The issue in the original post is that the context variable isn't parsing effectively as JSON. If we change the...