-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IN operator not correctly constructed in Query Builder Filter #830
Comments
I reported something similar . It's seems like "Clickhouse" connector is not working well |
@Guille-vn do you have a link to your issue? |
Sure |
Thank you for submitting this issue, I am able to reproduce this bug. This is an issue with the SQL generator converting the input to a string instead of splitting into a proper array, I will look into this and let you know when I push a fix. Thanks! |
We are currently using version 4.0.8 and still have the same problem. When I use the IN operator for ad hoc filters, it still outputs '(1,2,3)' instead of (1,2,3). We switched our dashboards from Altinity to this one a few weeks ago and didn't have similar issues before. I suspect the problem was only solved for a part of the plugin and not in general. |
What happened:
When constructing a query using Query Builder, if using the 'IN' operator for a filter, the generated SQL is not correct
What you expected to happen:
the generated SQL for XXX IN (1,2,3) would be expected to be
XXX IN (1,2,3)
Instead it produces
XXX IN '(1,2,3)'
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
n/a
Environment:
The text was updated successfully, but these errors were encountered: