Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL)
Description
if I change mdev_29008.test to use ORDER BY without aliases to an aggregate function, like
SELECT MIN(t2.a) AS f1, t1.b AS f2 FROM tbl_a AS t1 JOIN tbl_a AS t2 GROUP BY f2 ORDER BY MIN(t2.a), MAX(t2.a), f2; |
Then I can see that the spider will generate the query
select max(t1.`a`) ``,min(t1.`a`) ``,min(t1.`a`) `f1`,t0.`b` `b` from `auto_test_remote`.`tbl_a` t0,`auto_test_remote`.`tbl_a` t1 group by t0.`b` order by ``,``,t0.`b` |
which is clearly wrong, it doesn't distinguish between min and max. It needs to auto-generate names for aggregates as needed.
Also might apply to HAVING
Attachments
Issue Links
- relates to
-
MDEV-29480 spider group by handler wrong result on order by aggregate alias
- Closed
-
MDEV-26345 SELECT MIN on Spider table returns more rows than expected
- Closed