| Showing all 11 (Edit, Save, CSV, Feed) |
| ID# | Date | Type | Status | Sev | Version | Target | OS | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|
| 34310 | 2008-02-05 15:51 | Server: Optimizer | Verified (658 days) | S5 | 5.0.51a-log, 5.0.54 | Linux (SuSE 10.3) | Optimizer is inefficient by using ORDER BY function() and LIMIT | Igor Babaev | |
| 42094 | 2009-01-14 0:01 | Server: Optimizer | Verified (246 days) | S3 | 5.1 | Any | Optimizer chooses a wrong index when group by, order by and limit is present | Gleb Shchepa | |
| 42851 | 2009-02-13 23:27 | Server: Replication | Patch pending (13 days) | S3 | 5.1.31 | 5.1+ | Linux (Fedora Core 9) | Spurious "Statement is not safe to log in statement format." warnings | Daogang Qu |
| 43216 | 2009-02-26 10:13 | Server: Falcon | Verified (264 days) | S3 | 6.0.10 | 6.0-rc | Any | Trailing values between 0x00 and the pad char sort incorrectly when using LIMIT | Lars-Erik Bjørk |
| 45227 | 2009-06-01 0:48 | Server: Optimizer | Need Doc Info (11 days) | S3 | 5.4 | 5.4+ | Any | Queries with IN + condition, HAVING, ORDER BY 'pk' and LIMIT produce bad results | Evgeny Potemkin |
| 45373 | 2009-06-08 15:14 | Server: Optimizer | Verified (158 days) | S3 | 5.1.35-community, 5.1.36-bzr | Any | INDEX FOR GROUP BY is not used if there is a LIMIT clause in the query | Gleb Shchepa | |
| 46135 | 2009-07-12 21:03 | Server: Optimizer | Verified (70 days) | S2 | 5.0, 5.1, next, 6.0.0, 6.0.2, 5.1.36 | Any | LIMIT + JOIN problem | ||
| 46282 | 2009-07-18 17:12 | Server: Optimizer | Verified (129 days) | S3 | 5.4, 6.0 | Any | VAR and STD_DEV functions returning inconsistent results with addition of LIMIT | ||
| 46283 | 2009-07-18 17:22 | Server: General | Verified | S3 | 5.0, 5.1, 5.4, 6.0 | Any | COUNT() returning bad values when LIMIT 1 clause added to query | ||
| 46648 | 2009-08-11 13:41 | Server: Optimizer | Verified (99 days) | S3 | 5.1.32, 4.1, 5.0, 5.1, azalea bzr | Linux (2.6.28.7) | SQL_CALC_FOUND_ROWS kills performance with ORDER BY and LIMIT | ||
| 48118 | 2009-10-16 16:22 | Server: Optimizer | Verified | S3 | 5.1, 6.0 | Any | Server processing HAVING clauses incorrectly without a LIMIT clause |
| Showing all 11 (Edit, Save, CSV, Feed) |
