-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add backquotes to columns when executing dbt unit tests #868
Comments
So, I think technically you are supposed to set this on the columns: https://docs.getdbt.com/reference/resource-properties/quote However, I'm more and more feeling like we should just always backtick column names. @mikealfare, what are your thoughts on this? |
Oh, thank you for giving me that URL! I didn't know that page existed. After setting this config, I try to execute test again. |
I tried to execute test after setting it, but the same error occurred.
|
Thanks for reporting and following up. I'm thinking I'll move towards just always quoting, since there are places where I may have access to column names but not the 'quote' information anymore. I'll add a behavior flag for this for 1.9.1. |
Thank you for your response. I hope that a fixed version will be released. |
It doesn't look like I'll have this finished in time for 1.9.1, as my attempts to always backtick columns broke a bunch of tests. I'm still prioritizing this, but I don't think it will be ready until January. Apologies for any inconvenience. |
Describe the bug
I created using code like the following (Note that I used Japanese, that is non-ASCII character, for column names):
I defined the schema like the following, and created the csv file for this unit test:
After that, when I executed
dbt run
command, dbt runs failed with this error:I would appreciate you when you could tell me how I can solve this problem. However, I suppose that it's easiest way to change column names to english but I can't do it that way.
System information
The output of
dbt --version
:The operating system you're using :windows 10 (22H2)
The output of
python --version
:python 3.9.19Additional context
I found the similar issue. (#859)
The text was updated successfully, but these errors were encountered: