Bug #88053 | too few rows when query contains group_concat, left join, and no group by | ||
---|---|---|---|
Submitted: | 11 Oct 2017 9:05 | Modified: | 12 Oct 2017 5:08 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.7.19 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[11 Oct 2017 9:05]
Shane Bester
[11 Oct 2017 9:15]
MySQL Verification Team
Hello Shane, Thank you for the report and test case. Observed with 5.5.57, 5.6.37 and 5.7.19. Thanks, Umesh
[12 Oct 2017 5:08]
MySQL Verification Team
*** RLYSENG roy.lyseng 10/11/17 04:13 am *** This is not a bug: The reason for select a,group_concat(d)q from t left join s on c=a; to output a single row only is that there is no GROUP BY clause, and due to the group_concat() function, the query is implicitly aggregated into one row. The value chosen for 'a' is an arbitrary one.