Barry Pollard

That's probably not a bad idea. Though be aware you might want a different rules on each. L036 for example wouldn't be relevant for this SQL presumably as you actually...

This is tricky. Basicaly L026 works to make sure qualified columns only use tables in the from clause. This doesn’t really work for `STRUCT`s as impossible to know if it’s...

You are correct. It was just that, other than for BigQuery, it was not really necessary to test for b) (valid) since the combination of L026 and L027 would effectively...

So here's some SQL: ```sql SELECT t3.col1, col2 FROM table1 t1 JOIN table2 t2 ON t1.col1 = t2.col1 ``` This would potentially flag: - L026 - for `t3.col1` (but not...

At present only some of the `ALTER` statements have been implemented in the Snowflake dialect. Adding these is relatively easy (as detailed in the [Contributing Dialect Changes wiki](https://github.com/sqlfluff/sqlfluff/wiki/Contributing-Dialect-Changes)), but would...

> I expect the rule not to be triggered since in Oracle double quotes are required if an alias contains spaces OR if it contains lower-case chars. My understanding is...

Well oracle is case insensitive by default, and you need to explicitly add the quotes to change the default. This indicates to me what they consider best practice and matches...

BigQuery has this in it's dialect so could basically just copy it's definition and add some tests: https://github.com/sqlfluff/sqlfluff/blob/bc147334a8a85b1abdcc007868e7992288247880/src/sqlfluff/dialects/dialect_bigquery.py#L916-L936 > just notice: > > `* except()` command is supported by Databricks...

Agreed! The `ignore=parsing` is intended to still be able to lint the SQL around the area it can't understand (though note this can lead to sqlfluff misunderstanding the SQL which...

Those are sentences not words 😁 Each identifier part is handled as a unique token (do a `sqlfluff parse` to see the parts) and the rule applies at each identifier...