| Showing all 18 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 35002 | 2008-03-03 14:17 | 2018-09-09 20:45 | MySQL Server: DML | Verified (6169 days) | S2 | 5.1.23-rc/5.1BK/5.0/6.0 | Linux (2.6.22.9-61.fc6) | Any | Wrong results returned when using derived table and group by |
| 42948 | 2009-02-17 23:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5805 days) | S5 | 5.0.67-0ubuntu6, 6.0.11 | Linux (Ubuntu 8.10) | Any | MySQL Optimizer does not properly use Indexes on Views with "Group By" |
| 45373 | 2009-06-08 13:14 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified (5697 days) | S3 | 5.1.35-community, 5.1.36-bzr | Any | Any | INDEX FOR GROUP BY is not used if there is a LIMIT clause in the query |
| 46011 | 2009-07-07 14:05 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5217 days) | S3 | 5.1-bugteam | Any | Any | Regression after applying fix for bug #45828 |
| 52029 | 2010-03-13 12:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5421 days) | S5 | 5.1.44 | Any | Any | GROUP BY results in much slower query |
| 59557 | 2011-01-17 15:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5120 days) | S2 | 5.1, 5.5 | Any | Any | MySQL uses order of fields in GROUP BY when ORDER BY NULL is specified |
| 60023 | 2011-02-08 21:45 | 2014-05-22 12:13 | MySQL Server: Optimizer | Verified | S5 | 5.5.8 , 5.1.51 | Any | Any | No Loose Index Scan for GROUP BY / DISTINCT on InnoDB partitioned table |
| 61568 | 2011-06-20 14:22 | 2011-06-25 11:30 | MySQL Server: Stored Routines | Verified (4965 days) | S2 | 5.5.15, 5.5.13 | Any | Any | Result is not grouped on sequential store procedure runs |
| 67529 | 2012-11-09 0:20 | 2017-01-09 18:55 | MySQL Server: DML | Verified (4458 days) | S3 | 5.1.41, 5.1.67, 5.5.29, 5.7.0 | Any | Any | GROUP BY treats +0 and -0 as different values |
| 68072 | 2013-01-12 18:02 | 2013-01-13 15:08 | MySQL Server: Optimizer | Verified (4393 days) | S2 | 5.1, 5.5 | Any (Win64, CentOS Linux) | Any | MySQL 5.1 issue with timediff, group by on multiple columns, join, primary key |
| 69310 | 2013-05-23 11:47 | 2018-03-14 20:45 | MySQL Server: DML | Verified (4263 days) | S3 | 5.6, 5.0.97, 5.1.70, 5.5.32, 5.6.12, 5.7.2 | Any | Any | Valid SQL statement rejected in ONLY_FULL_GROUP_BY |
| 71189 | 2013-12-20 14:56 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (4052 days) | S3 | 5.5, any | Any | Any | Manual does not provide enough details on how loose index scan really works |
| 80455 | 2016-02-20 23:21 | 2016-02-21 22:05 | MySQL Server: Optimizer | Verified (3259 days) | S3 | 5.5, 5.6 | Linux | Any | Non-grouping field error with tables that have the same column names |
| 83596 | 2016-10-28 8:06 | 2016-11-21 13:51 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2985 days) | S2 | 5.6.27-ndb-7.4.8-cluster-gpl | CentOS (CentOS release 6.4) | Any | select with group_concat will resturn wrong result of bit fields |
| 98647 | 2020-02-18 13:06 | 2020-02-18 14:03 | MySQL Server: Optimizer | Verified (1801 days) | S3 | 5.7.29 | Windows | x86 | Bad SUM result with GROUP BY |
| 106312 | 2022-01-27 18:14 | 2022-02-09 13:20 | MySQL Server: Optimizer | Verified (1091 days) | S3 | 5.7 | Any (Ubuntu 20.04.3 LTS) | Any (Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz) | Huge value in GROUP BY clause cause unexpected output |
| 111415 | 2023-06-14 9:39 | 2023-06-19 14:12 | MySQL Server: Optimizer | Verified (584 days) | S3 | 8.0 | Any | Any | Correlated group query wrong result |
| 115040 | 2024-05-16 12:09 | 2024-10-29 10:09 | MySQL Server: Optimizer | Verified (252 days) | S3 | 8.0 | Any | Any | Incorrect result from lateral join with group by month/monthname function inside |
| Showing all 18 (Edit, Save, CSV, Feed) |
