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
Is your feature request related to a problem or challenge?
I found aggregation fuzzer are still hard to use when I act as an user currently.
Some points I noticed can be improved:
1. Aggregation function generation
Now it is still hard/possible to generate sql having multiple aggregated functions like:
SELECT count(string), sum(number) FROM xxx GROUP BY xxx;
It is due to aggregate_function and aggregate_arguments are set respectively. if we set mutiple aggregate_functions, columns in the respectly set aggregate_arguments may be not supported in some of the aggregate_functions.
For example,
If we set:
aggregate_arguments: [string, primitive]
aggregate_function: [sum, count]
Then wrong generated sql possible to be generated:
SELECT sum(string) FROM t GROUP BY xxx
Is your feature request related to a problem or challenge?
I found aggregation fuzzer are still hard to use when I act as an user currently.
Some points I noticed can be improved:
1. Aggregation function generation
Now it is still hard/possible to generate sql having multiple aggregated functions like:
It is due to
aggregate_function
andaggregate_arguments
are set respectively. if we setmutiple aggregate_functions
, columns in the respectly setaggregate_arguments
may be not supported in some of theaggregate_functions
.For example,
2. Group by columns ordering
Noticed by @jayzhan211 , it is hard to control the ordering of group by columns right now.
#15851 (comment)
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: