Error when using quoted column identifiers with snowflake
See original GitHub issueDescribe the bug
dbt run
and dbt test
finishes successfully, i.e. correct table and column specification, though lightdash cannot parse column specification from schema.yml. Note: Lightdash correctly sees table name, as per screenshot.
dbt_project.yml
:
quoting:
database: false
schema: true
identifier: true
Expected behavior
Lightdash correctly respect quoting, especially when using snowflake as a backend
Screenshots
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Identifier Requirements - Snowflake Documentation
If an object is created using a double-quoted identifier, when referenced in a query or any other SQL statement, the identifier must be...
Read more >Invalid Identifier Error in Snowflake When Performing a Join
If an object is created using a double-quoted identifier, the object can only be queried using the exact double-quoted identifier for that particular...
Read more >sql - Snowflake - Unable to Drop Column after Changing the ...
... double quotes around all the column names, but the issue is when I tried dropping a column from a table, Snowflake threw...
Read more >Column names quoted with backticks (eg reserved words) are ...
Column names quoted with backticks (e.g. reserved words) are quoted incorrectly in Utils.ensureQuoted #66. Closed. bclune ...
Read more >quote - dbt Developer Hub
The quote field can be used to enable or disable quoting for column names. ▷Changelog. Default. The default quoting value is false ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey @Vfisa thanks for opening the bug, just to keep you up to date. we’re making some final adjustments to charts this week. We’ll reprioritise again next Tuesday! In the mean time I’m going to take a look at the code to determine how complex this will be to support.
Quoting is such a headache 😰
Hi, any update on this?