Xi Chu

I just want to correct this. Only single quotes are allowed in our snowflake queries. I expect this rule should replace all double-quotes into single-quotes. > The problem is that...

> @XiChu2333: Could you write a script to search and replace double quotes with single quotes? > > I'm not sure I understand all this, but overall, this doesn't sound...

If we see the lint result here `L: 2 | P: 5 | L057 | Do not use special characters in identifiers.` The parser just simply treat all the double...

> 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...

> 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...

> 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...

> Sorry. I was wrong. I should take this back... Snowflake also support to use double quotes to make identifiers case-sensitive and to contain special characters. https://docs.snowflake.com/en/sql-reference/identifiers-syntax.html This makes the...

Maybe force_enable could still work as an option to take into column names. This force_enable is by default turned off. Any one who turn this on should know whether they...

Update: I upgrade my SQLFluff to version 1.0. The extra-new-line issue is solved. Could L016 also truncate "and" clause ?

I encounter some cases similar to this. I think it's more about new line. I would expect the parentheses that contain a subquery inside go a new line. One of...