| Showing all 17 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5896 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
| 115843 | 2024-08-15 8:26 | 2024-08-21 8:04 | MySQL Server: Optimizer | Verified (28 days) | S2 | 8.0.32, 8.0.39 | Any | Any | The incorrect calculation of 'select_limit' led to an incorrect index selection |
| 113135 | 2023-11-20 3:03 | 2023-11-20 15:34 | MySQL Server: DML | Verified (303 days) | S3 | 8.0 | Any | Any | DISTINCT JOIN ORDER BY statements ignore ORDER BY when tmp_table_size is small |
| 111415 | 2023-06-14 9:39 | 2023-06-19 14:12 | MySQL Server: Optimizer | Verified (457 days) | S3 | 8.0 | Any | Any | Correlated group query wrong result |
| 85533 | 2017-03-20 9:17 | 2017-03-20 11:42 | MySQL Server: DML | Verified (2739 days) | S3 | 5.7.16-log, 5.5.54, 5.6.35, 5.7.17 | Any | Any | Incorrect sorting result while substring_index function |
| 65899 | 2012-07-14 15:19 | 2012-08-25 15:59 | MySQL Server: Charsets | Verified (4445 days) | S2 | 5.x, 5.5.26 | Any | Any | "order by" clause returns wrong order result data (BIG5 COLLATE big5_chinese_ci) |
| 59557 | 2011-01-17 15:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4993 days) | S2 | 5.1, 5.5 | Any | Any | MySQL uses order of fields in GROUP BY when ORDER BY NULL is specified |
| 46011 | 2009-07-07 14:05 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5090 days) | S3 | 5.1-bugteam | Any | Any | Regression after applying fix for bug #45828 |
| 44943 | 2009-05-19 4:35 | 2011-02-16 23:43 | MySQL Server | Verified (5601 days) | S3 | 5.1.34, 4.1, 5.0, 5.1, 6.0 bzr | Any (NT) | Any | ORDER BY on SHOW INDEXES |
| 69100 | 2013-04-30 9:53 | 2015-03-15 20:45 | MySQL Server: InnoDB storage engine | Verified (4153 days) | S1 | 5.5.31-0, 5.5.30-1, 5.5.29-0, 5.5.25-1, 5.5.16, 5.5.30-1.1, 5.6.10, 5.0.97, 5.1.70, 5.5.29, 5.7.2 | Linux (Debian 6 / Debian 7 / Ubuntu 12.10 / Windows 8) | Any | CAST in IF function fails in some case |
| 69670 | 2013-07-04 11:37 | 2013-07-05 1:04 | MySQL Server: DML | Verified (4093 days) | S1 | 5.5.31/5.5.32 | Linux (Debian ) | Any | Dependent subquery with ORDER BY returns empty string |
| 34310 | 2008-02-05 14:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (3927 days) | S5 | 5.0.51a-log, 5.0.54, 5.6.14 | Linux | Any | Optimizer is inefficient by using ORDER BY function() and LIMIT |
| 46648 | 2009-08-11 11:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5511 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 |
| 34621 | 2008-02-16 21:05 | 2014-06-29 20:45 | Connector / ODBC | Verified (6052 days) | S2 | ODBC 5.1.2 - MySQL 5.0.51a | Windows (XP with SP2) | Any | ODBC - Update fails, if a "ORDER BY" clause is specified |
| 87644 | 2017-09-01 22:19 | 2022-09-06 8:01 | MySQL Server: Optimizer | Verified (2338 days) | S2 | 5.7.18 | CentOS (6 (x86_64)) | Any | Order by on 'datetime' column not working with LIMIT <row_count> |
| 100822 | 2020-09-12 14:39 | 2023-02-20 1:47 | MySQL Server: DML | Verified (1243 days) | S3 | 8.0/5.7/5.6 | Red Hat (7.4) | Any | the result of group_concat(field1 order by field2) is unexpect. |
| 87835 | 2017-09-22 8:19 | 2018-12-19 1:41 | MySQL Server: DML | Verified (2553 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 |
| Showing all 17 (Edit, Save, CSV, Feed) |
