| Showing all 9 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 30402 | 2007-08-14 8:35 | 2014-03-10 14:31 | MySQL Server: DML | Verified (3218 days) | S2 | 5.0.37 Community | Linux (RedHat 9.0) | Any | SELECT count(distinct) from mytable return 0 |
| 38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4809 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
| 46277 | 2009-07-17 21:33 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1, 5.4, 6.0 | Any | Any | differing results for equivalent queries using VAR_POP() & AVG() with DISTINCT |
| 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 |
| 65792 | 2012-07-03 2:19 | 2012-07-04 9:54 | MySQL Server: Optimizer | Verified (3373 days) | S5 | 5.1,5.5 | Any | Any | an unecessary Using temporary in distinct query |
| 79497 | 2015-12-02 16:41 | 2015-12-02 17:51 | MySQL Server: FULLTEXT search | Verified (2126 days) | S2 | 5.7, 5.6.29, 5.7.11, 5.7.9 | Ubuntu (14.04) | Any | Fulltext index on a given column causes empty set for 'distinct' query |
| 82308 | 2016-07-21 14:54 | 2016-07-21 17:54 | MySQL Server: MyISAM storage engine | Verified (1894 days) | S1 | 5.7 | Any | Any | use of DISTINCT with BIT and LONGTEXT leads to erroneous results |
| 87835 | 2017-09-22 8:19 | 2018-12-19 1:41 | MySQL Server: DML | Verified (1466 days) | S1 | 5.7.19 | Ubuntu (Ubuntu 16.04.2 LTS) | Any | the combination of SELECT DISTINCT and ORDER BY give wrong result for some data |
| 91418 | 2018-06-26 7:08 | 2018-09-07 13:32 | MySQL Server: Optimizer | Verified (1189 days) | S3 | 5.7,8.0.11, 5.7.22 | Any | Any | derived_merge causing inccorect results with distinct subquery and uuid() |
| Showing all 9 (Edit, Save, CSV, Feed) |
