Showing 1-30 of 148 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
43 | 2003-01-27 18:54 | 2008-10-03 9:47 | MySQL Server: Optimizer | Can't repeat (5683 days) | S3 | 3.23, 4.0 | Any (all) | Any | Join does not use indexes in case there is no cardinarity data |
7516 | 2004-12-23 20:26 | 2005-11-26 13:02 | MySQL Server: Optimizer | Can't repeat (6725 days) | S2 | 4.0.25 and 4.1.10a | Linux (Linux (SuSE 8.2)) | Any | Wrong sort order when ORDER BY includes an ENUM column |
8168 | 2005-01-27 18:09 | 2020-02-05 15:35 | MySQL Server: Optimizer | Can't repeat (1541 days) | S3 | 5.0-bk | Any | Any | HELP commands processing different from regular with --ps-protocol |
8772 | 2005-02-24 10:31 | 2005-02-24 10:39 | MySQL Server: Optimizer | Can't repeat (7000 days) | S2 | 5.0.2-alpha | Linux (Linux) | Any | Whan using MEMORY tables with HASH indexes can't insert multiply times in to me |
10312 | 2005-05-02 11:51 | 2020-01-14 21:56 | MySQL Server: Optimizer | Can't repeat (1563 days) | S2 | 5.0.4 | Linux (linux debian) | Any | subquery cant be optimized correctly |
11521 | 2005-06-23 6:35 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5245 days) | S2 | 4.1 and 5.x | Any (all) | Any | Negative integer keys incorrectly substituted for 0 during range analysis. |
11906 | 2005-07-13 9:52 | 2005-07-13 17:39 | MySQL Server: Optimizer | Can't repeat (6861 days) | S2 | 4.1.11-standard-log | 4.1.11-dec-osf5.1b-alphaev67 | Any | Using a variable instead of a constant gives incorrect results in a query join |
12962 | 2005-09-03 6:22 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5260 days) | S2 | 4.1.14 | Linux (Linux & Windows) | Any | Type of column chages if the result is ordered or not |
14070 | 2005-10-17 11:03 | 2014-01-24 13:20 | MySQL Server: Optimizer | Can't repeat (3744 days) | S2 | 5.0.16, 5.0.15, 4.1.14, 5.1 | Linux (Linux) | Any | MySQL hangs on "Copying to tmp table" |
17590 | 2006-02-20 17:44 | 2006-02-23 9:32 | MySQL Server: Optimizer | Can't repeat (6636 days) | S2 | 5.1.7-beta | Any (All) | Any | Different key-len and # rows reported on all platforms |
20873 | 2006-07-05 21:14 | 2014-01-24 12:26 | MySQL Server: Optimizer | Can't repeat (3744 days) | S3 | 5.0.24-BK, 5.0.22 | Linux (Linux, freebsd) | Any | group_concat with distinct using weekday |
23731 | 2006-10-27 17:15 | 2006-11-28 10:56 | MySQL Server: Optimizer | Can't repeat (6358 days) | S5 | 5.1.11 | Linux (Linux RH ES 3.0) | Any | The optimizer does not choose an appropriate key for table join in some cases |
26925 | 2007-03-07 17:19 | 2007-04-26 12:52 | MySQL Server: Optimizer | Can't repeat (6209 days) | S3 | 4.1.15 | Linux (Linux 2.6.8-022stab078-9) | Any | Empty result in MAX after creation of KEY |
26966 | 2007-03-08 17:27 | 2007-09-07 9:13 | MySQL Server: Optimizer | Can't repeat (6075 days) | S3 | 5.0.38-enterprise-gpl-log | Linux (Ubuntu 6.06 LTS) | Any | Optimizer does not select range access over ref in some specific cases |
27109 | 2007-03-14 4:15 | 2007-03-14 8:11 | MySQL Server: Optimizer | Can't repeat (6252 days) | S3 | 4.0.13 | Windows (windows) | Any | High CPU/Memory Usage |
28338 | 2007-05-09 18:50 | 2016-01-18 9:58 | MySQL Server: Optimizer | Can't repeat (3020 days) | S2 | 5.0.42-BK, 5.0.37 | Any | Any | Optimizer doesn't choose the correct plan on a 3 table join |
28950 | 2007-06-07 15:22 | 2007-06-07 18:11 | MySQL Server: Optimizer | Can't repeat (6167 days) | S3 | 5.0.40, 5.0.41 | Linux (x86, x86-64) | Any | Using EXISTS and a GROUP BY incorrectly yields no results |
29158 | 2007-06-17 7:46 | 2007-06-17 14:35 | MySQL Server: Optimizer | Can't repeat (6157 days) | S1 | 5.0.42 | Windows | Any | crash on cleanup after out of memory scenerio |
29577 | 2007-07-05 16:14 | 2007-07-11 21:08 | MySQL Server: Optimizer | Can't repeat (6133 days) | S1 | 5.0.42 | Any | Any | mysqld can crash on some queries when server runs out of memory |
30672 | 2007-08-28 15:49 | 2007-10-12 14:12 | MySQL Server: Optimizer | Can't repeat (6040 days) | S3 | 5.1.20 | Linux | Any | Wrong optimization when using a join and a function |
33037 | 2007-12-06 12:49 | 2007-12-07 8:43 | MySQL Server: Optimizer | Can't repeat (5984 days) | S5 | 5.0.22-pro-nt-log | Any | Any | Different and much slower access plan used for select when used with insert into |
33592 | 2007-12-30 23:31 | 2007-12-30 23:38 | MySQL Server: Optimizer | Can't repeat (5961 days) | S3 | 5.0.45 | Linux | Any | index not being used with user-defined function in where clause |
34753 | 2008-02-21 23:28 | 2008-02-22 4:28 | MySQL Server: Optimizer | Can't repeat (5907 days) | S2 | 5.0.22 | Linux | Any | Optimizer doesn't see Index on text field. |
36914 | 2008-05-23 12:02 | 2008-05-23 12:50 | MySQL Server: Optimizer | Can't repeat (5816 days) | S2 | mysql-5.0.51a-linux-i686-glibc23 | Linux (SuSE 10.3 32 bit) | Any | ORDER BY DESC ignored in Query Result |
37439 | 2008-06-17 2:00 | 2008-07-18 16:10 | MySQL Server: Optimizer | Can't repeat (5760 days) | S3 | 5.0.27-community-nt | Windows | Any | Incorrect output order from ORDER BY using 2 field index in MEMORY BTREE |
38010 | 2008-07-10 9:36 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5399 days) | S2 | 6.0,5.4 | Any | Any | Wrong result returned when outer join, semijoin and "use index" |
38056 | 2008-07-11 19:14 | 2014-11-03 14:22 | MySQL Server: Optimizer | Can't repeat (3461 days) | S3 | 4.1, 5.0, 5.1, 6.0-bk, | Any | Any | EXPLAIN doesn't report "Using where" for a LEFT JOIN query with ON expression |
38576 | 2008-08-05 16:07 | 2008-08-05 19:20 | MySQL Server: Optimizer | Can't repeat (5742 days) | S2 | 5.1.23 | Linux (CentOS release 5 (Final)) | Any | Incorrect LIMIT behavior with ORDER BY |
38993 | 2008-08-24 19:03 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5599 days) | S5 | 5.1.26, 5.0.67 | Any | Any | Inconsistent behaviour of optimizer in "statistics" phase |
39424 | 2008-09-12 17:18 | 2013-01-10 11:24 | MySQL Server: Optimizer | Can't repeat (4123 days) | S3 | 5.1/5.0 | Any | Any | EXPLAIN shows wrong access method for FROM subquery with ORDER BY |
Showing 1-30 of 148 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |