| Showing all 11 (Edit, Save, CSV, Feed) |
| ID# | Date | Type | Status | Sev | Version | Target | OS | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|
| 28695 | 2007-05-26 0:30 | Server: Views | Verified (718 days) | S3 | 5.0.41 | Mac OS X | spurious error when counting rows in view with order by clause | Gleb Shchepa | |
| 34310 | 2008-02-05 15:51 | Server: Optimizer | Verified (656 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 | |
| 34621 | 2008-02-16 22:05 | Connector/ODBC | Verified (638 days) | S2 | ODBC 5.1.2 - MySQL 5.0.51a | Microsoft Windows (XP with SP2) | ODBC - Update fails, if a "ORDER BY" clause is specified | Jess Balint | |
| 38397 | 2008-07-27 22:13 | Server: Optimizer | Verified (482 days) | S3 | 5.1.26, 5.0.62 | Any | select distinct + order by desc is executed inefficiently | Gleb Shchepa | |
| 39287 | 2008-09-06 14:56 | Server: Charsets | Verified (441 days) | S3 | 5.0.51a, 5.0.67, 5.1.26 | Linux (Ubuntu Hardy 8.04 AMD64) | Binary conversion of a multi-byte encoded string leads to wrong sort order | Alexander Barkov | |
| 41090 | 2008-11-28 13:17 | Server: Optimizer | Verified (359 days) | S3 | 5.0.41-community-nt, 5.0.70, 5.1.30, 6.0.7 | Microsoft Windows (XP) | ORDER BY truncates GROUP_CONCAT result | Gleb Shchepa | |
| 42094 | 2009-01-14 0:01 | Server: Optimizer | Verified (244 days) | S3 | 5.1 | Any | Optimizer chooses a wrong index when group by, order by and limit is present | Gleb Shchepa | |
| 44943 | 2009-05-19 6:35 | Server | Verified (187 days) | S3 | 5.1.34, 4.1, 5.0, 5.1, 6.0 bzr | Any (NT) | ORDER BY on SHOW INDEXES | ||
| 44969 | 2009-05-20 1:31 | Server: Optimizer | Verified (173 days) | S5 | 5.1.34, 5.1.35, 6.0 bzr | Linux (x64) | index not being used anymore with order by query | Gleb Shchepa | |
| 46011 | 2009-07-07 16:05 | Server: Optimizer | Verified | S3 | 5.1-bugteam | 5.4+ | Any | Regression after applying fix for bug #45828 | Evgeny Potemkin |
| 46648 | 2009-08-11 13:41 | Server: Optimizer | Verified (97 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 |
| Showing all 11 (Edit, Save, CSV, Feed) |
