Barry Pollard

It's because of the different way they are parsed. ``` [L: 1, P: 14] | table_reference: [L: 1, P: 14] | identifier: '`bigquery-public-data.pypi.file_downloads`' ``` versus: ``` [L: 1, P: 14]...

Well, given that we've now just allowed dashes by default in BigQuery I don't think we really need to do any more here do we?

Yeah it's a bit of an anomaly all right, but at the end of the day it is working as intended. Even if by accident rather than by design! So...

Interestingly using 1 indentation avoids the error, and even using `sqlfluff fix` replaces the 2 indentations with 1 indentation. And worse still, using 0 indentations still surfaces an error (the...

Please provide the contents of testfile.sql

The problem is that this is not recognised as a string literal but as a column name and L064 only deals with string literals: ``` $ sqlfluff parse --dialect snowflake...

Ah, that won't work. The rules only work on parsable code (so it can understand it and know what is a literal and what is not). Double-quoted strings are not...

It doesn’t treat quotes as part of the identifier. They are listed as quoted identifiers. But it does point to the start of the symbol (including quotes) for reporting rule...

Ok so there it’s actually complaining about the space, not the quotes. Remove it and you’ll see the error goes away. I know it’s a little confusing since it gives...

So, how to resolve this issue. L064 only looks at quoted literals and, because double quotes are not valid for quoted literals in Snowflake SQLFluff is parsing those as columns...