I recently upgraded to 2024.1 from 2023.1 and when I view my SQL code in Visual Query Builder, it adds "double quotes" (Teradata & Oracle) and [brackets] (SQL Server) to my code. For example,
Select DB.FIRST_NAME, DB.LAST_NAME FROM DATALAKE.TABLE DB
gets converted to
Select "DB"."FIRST_NAME", "DB"."LAST_NAME" FROM "DATALAKE"."TABLE" "DB"
1.) Is this something that was intentionally added in 2024.1 or should I consider this a new issue?
2.) If it's not intentional, does anyone know how to resolve it?
Is it affecting your running of the workflow?
I think this is an intentional behavior for cases where field names have spaces.
I think that makes sense @ntakeda
@kwhitaker if your workflow is still running as normal, I wouldn't be too concerned with this
Y well the double quote thing drives me nuts and clutters my code. It also breaks many of my dynamic replace statements and I have to perpetually clean the double quotes out. I wish it was a setting you could turn off.
this is kind of odd --- not just because the quotes popped up but because quoting should be controlled at the odbc driver level ---> not by Alteryx. Alteryx should be following driver precedence here.... so if you have quotes set up in your driver --- you should see quotes in Alteryx and vice versa.
@usroycow1 what DB --- and how is your driver set up?
Double quotes are normally used to define case-sensitive identifiers like column names "myColumn". They are also used to escape special characters within a string
User | Count |
---|---|
106 | |
85 | |
76 | |
54 | |
40 |