Showing all 13 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
45373 | 2009-06-08 13:14 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified (5721 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 |
46135 | 2009-07-12 19:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5321 days) | S2 | 5.0, 5.1, next, 6.0.0, 6.0.2, 5.1.36 | Any | Any | LIMIT + JOIN problem |
46283 | 2009-07-18 15:22 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1, 5.4, 6.0 | Any | Any | COUNT() returning bad values when LIMIT 1 clause added to query |
46648 | 2009-08-11 11:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5662 days) | S3 | 5.1.32, 4.1, 5.0, 5.1, azalea bzr | Linux (2.6.28.7) | Any | SQL_CALC_FOUND_ROWS kills performance with ORDER BY and LIMIT |
50168 | 2010-01-08 2:16 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5513 days) | S3 | 5.0,5.1 | Any | Any | The value of 'rows' in EXPLAIN output is not accurate for LIMIT |
52613 | 2010-04-06 9:04 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5430 days) | S2 | mysql-5.1-telco-7.0 | Any | Any | Inconsistent and permanent error when attribute name is to long for PK |
55211 | 2010-07-13 13:50 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (5332 days) | S2 | 5.1+ | Any | Any | INSERT...SELECT...LIMIT...UNION should be marked unsafe |
34310 | 2008-02-05 14:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4078 days) | S5 | 5.0.51a-log, 5.0.54, 5.6.14 | Linux | Any | Optimizer is inefficient by using ORDER BY function() and LIMIT |
82560 | 2016-08-12 3:32 | 2016-08-16 10:10 | MySQL Server: DML | Verified (3110 days) | S3 | 5.5.51, 5.6.32, 5.7.14 | Linux | Any | nested limit produces counter intuitive result |
87644 | 2017-09-01 22:19 | 2022-09-06 8:01 | MySQL Server: Optimizer | Verified (2489 days) | S2 | 5.7.18 | CentOS (6 (x86_64)) | Any | Order by on 'datetime' column not working with LIMIT <row_count> |
76398 | 2015-03-19 20:27 | 2020-04-11 2:21 | MySQL Server: InnoDB storage engine | Verified (1772 days) | S3 | 5.6.23, 5.6.25, 5.5.44 | Any (CentOS, Mac OS X) | Any | MySQL doing full scan depending on limit value with ORDER BY query |
104127 | 2021-06-28 7:00 | 2021-06-28 7:19 | MySQL Server: Optimizer | Verified (1329 days) | S2 | 8.0, 8.0.25 | Any | Any | output count is unexpected when limit clause is used in CTE |
110848 | 2023-04-27 15:04 | 2023-05-03 9:59 | MySQL Server: Optimizer | Verified (655 days) | S5 | 8.0.28, 8.0.33 | Any | Any | missing considering on order by and limit clause in cost calculation |
Showing all 13 (Edit, Save, CSV, Feed) |