[Bug] [UI] SQL node cannot be saved in certain situations #16915
Description
Search before asking
- I had searched in the issues and found no similar issues.
What happened
When using the SQL node, several situations have been found that prevent saving:
-
Using CASE WHEN statements within aggregate functions, e.g.,
SUM(CASE WHEN ... THEN ... END).
But the formatmax(case 1 when 1 then 2 end)can be saved normally -
When the SQL includes the aggregate function
GROUP_CONCAT(), see issue [Bug] [UI] sql node function group_concat don't save define #14132 .
-
Formatting, see issue The format of the sql statement prevents the workflow from being saved #15559 .
The same SQL statement in the following format can be saved.
Deployed on Kubernetes, both 3.1.x and 3.2.x have these issues.
I hope this issue can be resolved soon. Thank you!
What you expected to happen
If there is no risk of SQL injection, then regardless of the format, it should be saved normally.
How to reproduce
As above.
Anything else
No response
Version
3.1.x
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct