Showing all 29 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
32700 | 2007-11-25 15:24 | 2008-07-28 19:25 | MySQL Server: Optimizer | Not a Bug (5757 days) | S3 | 5.0.45, 4.1, 5.1, 6.0 BK | Linux (5.0.45-Debian_1ubuntu3-log) | Any | STRAIGHT_JOIN doesn't force join order |
26003 | 2007-02-01 9:18 | 2007-08-18 2:43 | MySQL Server: Optimizer | Not a Bug (6102 days) | S4 | 5.0.27, 4.1.x | Linux (Linux, Windows) | Any | "ref_or_null" access method is used while "range" gives faster execution |
28483 | 2007-05-17 1:22 | 2007-08-17 18:58 | MySQL Server: Optimizer | Not a Bug (6103 days) | S2 | v5.1 | Any | Any | The optimizer retrieves much more extra records |
30372 | 2007-08-11 16:02 | 2007-08-11 23:14 | MySQL Server: Parser | Not a Bug (6109 days) | S3 | 5.0.45/4.1/5.1 | Linux | Any | STRAIGHT JOIN somehow loses table/column references in SELECT list |
30076 | 2007-07-26 15:46 | 2007-08-10 10:37 | MySQL Server | Not a Bug (6110 days) | S4 | all | Any | Any | Unexpected output in SELECT * FROM test ORDER BY foo DESC LIMIT 75, 15; |
29357 | 2007-06-26 11:34 | 2007-08-06 7:39 | MySQL Server: Optimizer | Not a Bug (6114 days) | S2 | 5.1.19-beta-log MySQL, 5.0 BK | Any | Any | Filtering on view with group don't works. |
28871 | 2007-06-04 11:30 | 2007-06-29 20:52 | MySQL Server: Optimizer | Not a Bug (6152 days) | S3 | 5.0.42, 5.1.19 | Any | Any | restriction using where in (...) is faster with big in set |
28979 | 2007-06-08 15:13 | 2007-06-20 8:57 | MySQL Server: Data Types | Not a Bug (6161 days) | S3 | 5.0.44-BK, 5.0.41 | Windows | Any | Floats/Doubles in scientific notation don't work in WHERE clauses |
28955 | 2007-06-07 18:42 | 2007-06-09 5:41 | MySQL Server: General | Not a Bug (6172 days) | S2 | 5.0.44-BK, 4.1.7 | Linux | Any | WITH ROLLUP returning wrong values |
24864 | 2006-12-06 19:13 | 2007-03-13 19:03 | MySQL Server: Optimizer | Not a Bug (6260 days) | S5 | 5.0.32-BK, 5.0.18 | Linux (Linux) | Any | Functions with a known result are NOT 'resolved' |
26528 | 2007-02-21 15:02 | 2007-02-22 16:21 | MySQL Server: Optimizer | Not a Bug (6279 days) | S3 | 5.0.34, 5.0.27 | Windows (Windows) | Any | Optimizer produces inefficient execution plan on 5.0.x compared to 4.1.21 |
13874 | 2005-10-09 16:23 | 2006-10-27 0:42 | MySQL Server: Optimizer | Not a Bug (6397 days) | S3 | 4.1.14, 5.0.13, 5.0.15-BK | Linux (Linux, Windows, FreeBSD) | Any | Incorrect subquery handling in "exists" |
20944 | 2006-07-10 15:25 | 2006-10-19 2:13 | MySQL Server: Optimizer | Not a Bug (6405 days) | S2 | 4.1.22-BK, 4.1.20, 5.0.22, 5.0.25-BK | Linux (Linux, freebsd) | Any | optimizer estimates more rows if condition gets narrowed / combined key / range |
21153 | 2006-07-19 15:10 | 2014-02-12 9:06 | MySQL Server | Not a Bug (6469 days) | S2 | 5.0.21-standard | Linux (linux) | Any | Join with many tables hangs mysql (and taking 100% cpu) |
20203 | 2006-06-01 13:45 | 2006-07-06 1:45 | MySQL Server: Views | Not a Bug (6510 days) | S3 | 5.0.22, 4.1.21-BK | Any (All) | Any | SEC_TO_TIME(SUM(TIME_TO_SEC( doesn't work correctly with a VIEW |
20523 | 2006-06-18 18:02 | 2006-07-06 0:15 | MySQL Server | Not a Bug (6510 days) | S3 | 5.1.12-beta-debug/4.1BK/5.0BK/5.1BK | Linux (SUSE 10.0 / 64-bit) | Any | Correlated subquery treats <=> as = |
20128 | 2006-05-29 15:55 | 2006-06-30 11:14 | MySQL Server: Optimizer | Not a Bug (6516 days) | S2 | 5.0 | Any | outer JOIN + GROUP BY: wrong result | |
15457 | 2005-12-03 14:19 | 2005-12-05 21:49 | MySQL Server | Not a Bug (6723 days) | S3 | 5.0.17-BK, 5.1.3 | Linux (Linux) | Any | full join not work |
11713 | 2005-07-03 20:36 | 2005-07-21 14:51 | MySQL Server: Optimizer | Not a Bug (6860 days) | S3 | 4.1-bk | Any | OUTER JOIN incorrectly converted to INNER for complex WHERE clause | |
11936 | 2005-07-14 12:46 | 2005-07-17 18:36 | MySQL Server: Optimizer | Not a Bug (6864 days) | S2 | 5.0.7-beta-nt/5.0.10 BK | Any (any) | Any | Lock table failing create table ....select |
10266 | 2005-04-29 15:47 | 2005-06-09 17:17 | MySQL Server: Optimizer | Not a Bug (6902 days) | S2 | 4.1 | Windows (Windows 2000) | Any | Order of multiple left joins matters? |
10512 | 2005-05-10 14:21 | 2005-05-17 12:27 | MySQL Server: Optimizer | Not a Bug (6925 days) | S2 | 4.0.25 forward | Any | Optimizer selecting wrong index with composite indexes | |
9689 | 2005-04-06 17:37 | 2005-04-22 21:10 | MySQL Server: Optimizer | Not a Bug (6950 days) | S3 | 4.1.11 | Any (*) | Any | wrong result for subselect in on duplicate key update (query cache) |
4100 | 2004-06-11 0:27 | 2004-08-24 23:57 | MySQL Server | Not a Bug (7191 days) | S3 | 4.0.20 | Any (all) | Any | Optimizer defficiency sorting on fields from different tables |
2243 | 2003-12-31 5:46 | 2004-02-02 4:42 | MySQL Server | Not a Bug (7395 days) | S3 | 3.23.58/4.0.16 | Linux (linux) | Any | bad key selection implies filesort |
2022 | 2003-12-05 9:00 | 2003-12-10 18:26 | MySQL Server | Not a Bug (7449 days) | S2 | 4.0.11 gamma | Windows (Windows 2000) | Any | Query Optimizer occaisionally uses wrong plan on the same query |
904 | 2003-07-23 20:53 | 2003-08-07 22:21 | MySQL Server: MyISAM storage engine | Not a Bug (7574 days) | S1 | 4.0.14 | Linux (debian linux) | Any | query jumped from 4 seconds to several minutes, join order changed in explain |
580 | 2003-06-04 2:50 | 2003-06-26 9:54 | MySQL Server | Not a Bug (7616 days) | S2 | 4.0 | Any | Join is not optimized well if IN (<VALUES>) is used | |
566 | 2003-06-02 4:21 | 2003-06-13 9:06 | MySQL Server | Not a Bug (7629 days) | S3 | 4.0.13-Max | Linux (Linux) | Any | Possible optimization bug with LEFT JOIN |
Showing all 29 (Edit, Save, CSV, Feed) |