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
When using the table chart and adding a derived column by using "Custom SQL" and using certain syntax that uses keywords that may be mistaken for a subquery I am unable to use the custom SQL.
How to reproduce the bug
Add any PostgreSQL datasource with a INTERVAL column (duration)
Add a table chart
Add a column with Customer SQL option and the following query: extract(epoch FROM duration) * 1000
See error:
Expected results
The column should have been calculated since there is no subquery involved.
Closing this issue as the feature flag seems to resolve it. @fmannhardt feel free to reopen the issue if that's not the case. I authored #25161 to include a note in UPDATING.md about the feature flag.
When using the table chart and adding a derived column by using "Custom SQL" and using certain syntax that uses keywords that may be mistaken for a subquery I am unable to use the custom SQL.
How to reproduce the bug
extract(epoch FROM duration) * 1000
Expected results
The column should have been calculated since there is no subquery involved.
Actual results
See step 3.
Environment
(please complete the following information):
Checklist
Make sure to follow these steps before submitting your issue - thank you!
(according to the 2.1.1 changelog this has not been fixed)
The text was updated successfully, but these errors were encountered: