Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Snowflake, Postgres: Parse failure on concatention operator `||`
See original GitHub issueSearch before asking
- I searched the issues and found no similar issues.
What Happened
Concatenate operand || incorrectly parsed as two pipes. Both Snowflake and Postgres recognize || as concatenation operand, thus 'a' || 'b' -- => 'ab'. SQLFluff blames it’s incorrect syntax.
Expected Behaviour
'a' || 'b' should pass linting
Observed Behaviour
'a' || 'b' fails linting with:
Expected single whitespace between pipe ‘|’ and pipe ‘|’.
How to reproduce
echo “SELECT ‘a’ || ‘b’ AS c;” | sqlfluff lint --dialect postgres --disable-progress-bar - echo “SELECT ‘a’ || ‘b’ AS c;” | sqlfluff lint --dialect snowflake --disable-progress-bar -
Dialect
Snowflake Postgres
Version
sqlfluff, version 1.4.3 Python 3.10.9
Configuration
[sqlfluff] templater = jinja
Are you willing to work on and submit a PR to address the issue?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project’s Code of Conduct
Issue Analytics
- State:
- Created 9 months ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
SQLFluff 1.4.4 has been released with this fixed in it.
Apologies!
FYI adding this to your config fixes it:
We’re adding it to the default config in #4168 and releasing another fix tonight, but if you can’t wait then apply above addition to your config.