You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Quoting column names as done in here causes an error on bigquery. In general I don't think SqlRender supports quoted column names. I'm not sure this is documented anywhere but after talking with @schuemie this is my understanding. To discover the error you would need to run your code on BigQuery.
To Reproduce
Run any SQL that quotes column names with double quotes on bigquery using DatabaseConnector and SqlRender.
Screenshots
My suggestion would be to remove quotes around column names from all OHDSI-SQL.
The text was updated successfully, but these errors were encountered:
I'm also getting this error. 1024 characters does not seem like a lot. @schuemie Have you seen this before? The stratified person sql query is around 1075 characters.
Ah, I think you are splicing a large number of person_ids into the query and it is making the query too long.
Yes, don't use quotes for column names. That makes them very hard to port across database platforms.
Many platforms have issues when an IN clause contains too many items. As a general rule of thumb, if the list of items may exceed 100, upload a temp table and join with that instead.
Describe the bug
Quoting column names as done in here causes an error on bigquery. In general I don't think SqlRender supports quoted column names. I'm not sure this is documented anywhere but after talking with @schuemie this is my understanding. To discover the error you would need to run your code on BigQuery.
To Reproduce
Run any SQL that quotes column names with double quotes on bigquery using DatabaseConnector and SqlRender.
Screenshots
My suggestion would be to remove quotes around column names from all OHDSI-SQL.
The text was updated successfully, but these errors were encountered: