Showing 1-30 of 140 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
21104 | 2006-07-18 2:05 | 2006-09-08 8:25 | MySQL Server | Not a Bug (6411 days) | S3 | 5.0.25-BK, 5.0.18 | Linux (Linux) | Any | R-Tree Index Incorrectly Optimized When Table Has One Row |
21903 | 2006-08-29 13:37 | 2006-09-25 11:01 | MySQL Server | Can't repeat (6394 days) | S2 | 5.0.24 | Linux (Fedora Core 3) | Any | BETWEEN doesn't cast dates correctly |
21992 | 2006-09-04 14:12 | 2006-09-05 9:46 | MySQL Server | Duplicate (6414 days) | S2 | 4.1.21 | Any (all) | Any | ORDER BY Does not Sort rows |
21314 | 2006-07-27 13:11 | 2012-05-18 20:19 | MySQL Server | Duplicate (6372 days) | S3 | 5.0.23 | Any (any) | Any | Stored functions in constant context not optimized to constants |
21486 | 2006-08-07 16:57 | 2006-11-01 10:12 | MySQL Server: Optimizer | No Feedback (6357 days) | S2 | 5.0.22 | Linux (Linux) | Any | No index merge for ENUM columns |
21698 | 2006-08-17 15:07 | 2006-09-25 18:02 | MySQL Server: Optimizer | Closed (6394 days) | S2 | 5.0.24 | Any | ASCII() function results are not respected in a WHERE clause | |
24056 | 2006-11-07 18:42 | 2006-12-09 18:23 | MySQL Server: Optimizer | Closed (6319 days) | S3 | Any | subselect.test fails in 5.0-opt on 64 bit platforms after fix for BUG#8804 | ||
22902 | 2006-10-02 19:28 | 2007-07-30 19:15 | MySQL Server: Documentation | Closed (6086 days) | S3 | 5.0.24, 5.1 BK | Linux (Linux) | Any | Query not able to use an index when comparing against results of SYSDATE() |
25798 | 2007-01-23 19:19 | 2007-07-09 0:58 | MySQL Server | Closed (6107 days) | S2 | 5.0.33, 5.0bk, 5.1bk | Linux (Linux) | Any | Incorrect results with the index merge union access algorithm and InnoDB tables |
25459 | 2007-01-08 2:39 | 2007-02-28 13:34 | MySQL Server: Optimizer | No Feedback (6238 days) | S3 | 5.0 | Any (any) | Any | InnoDB prefers table scan over using primary key |
26624 | 2007-02-25 21:25 | 2007-04-24 1:39 | MySQL Server: Optimizer | Closed (6183 days) | S2 | 5.0.38 4.1.23 | Any (*) | Any | high mem usage (crash) in range optimizer (depends on order of fields in where) |
26625 | 2007-02-25 21:49 | 2007-03-31 23:07 | MySQL Server | Closed (6207 days) | S1 | 5.2.4BK, 5.1.17BK, 5.0.38BK 4.1.23BK | Any (*) | Any | crash in range optimizer (out of mem) Bug #26624 |
27316 | 2007-03-21 4:20 | 2012-01-18 1:00 | MySQL Server: Optimizer | No Feedback (4454 days) | S3 | 4.1.2 | Linux (Linux) | Any | LEFT JOIN fails to use INDEX in 4.1.2 (used to work in 3.23) |
27975 | 2007-04-20 11:20 | 2013-01-16 16:17 | MySQL Server: Optimizer | Closed (4089 days) | S3 | 5.0.38, 5.0.44, 4.1, 5.0, 5.1, 5.2 BK | Linux (RHEL 4) | Any | optimizer error after discovering impossible where clause in a large view |
28189 | 2007-05-02 1:18 | 2007-05-15 2:51 | MySQL Server: Optimizer | Closed (6162 days) | S3 | 5.0.40, 5.1.18 | Any | Any | optimizer issue on Innodb tables |
26966 | 2007-03-08 17:27 | 2007-09-07 9:13 | MySQL Server: Optimizer | Can't repeat (6047 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 |
26232 | 2007-02-09 17:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6251 days) | S3 | 4.1.22, 5.0.34, 5.0.36-BK | Linux (Linux) | Any | review of bug #20944 / proof of concept attached |
28612 | 2007-05-23 7:30 | 2007-06-24 13:27 | MySQL Server: Optimizer | No Feedback (6122 days) | S5 | 5.0.37 | Any | Any | Optimizer does not use index for BETWEEN in a JOIN condition |
29443 | 2007-06-29 13:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4914 days) | S3 | 5.1.19 | Any | Any | cost calculations are off |
30584 | 2007-08-23 3:31 | 2022-09-04 20:45 | MySQL Server: Optimizer | Duplicate (5544 days) | S5 | 5.0.37,5.1.22 | Any | Any | delete with order by and limit clauses does not use limit efficiently |
30659 | 2007-08-28 1:03 | 2007-08-31 9:59 | MySQL Server: Optimizer | Can't repeat (6054 days) | S3 | 5.2.6 | Linux (2.6.20) | Any | 300% Performance Regression 5.0.45 -> 5.2.6 on Correlated Subquery |
30684 | 2007-08-29 8:38 | 2007-09-05 11:03 | MySQL Server: Optimizer | Not a Bug (6049 days) | S3 | 5.0.45 | Any | Any | Optimizer simply does a full table scan if a join is involved |
31094 | 2007-09-19 10:28 | 2007-11-13 18:52 | MySQL Server: Optimizer | Closed (5980 days) | S2 | 5.1 | Any | Any | Forcing index-based sort doesn't work anymore if joins are done |
31648 | 2007-10-16 19:01 | 2012-08-30 11:22 | MySQL Server: Optimizer | Can't repeat (4228 days) | S2 | 5.1.22, 5.0.50 | Any | Any | full table scans being done when range should be used |
31335 | 2007-10-02 10:27 | 2007-11-02 12:03 | MySQL Server: MyISAM storage engine | No Feedback (5991 days) | S2 | 5.0.12 | Any | Any | Multi-Update Vers. >= 5.0.12 ignores Rows / Just updates 1 Row |
28801 | 2007-05-31 9:51 | 2007-12-02 20:12 | MySQL Server: Optimizer | Duplicate (5961 days) | S2 | 5.1.20 | Windows | Any | vs debug warnings: stack around variable 'buf' was corrupted |
32006 | 2007-10-31 20:37 | 2007-11-15 3:34 | MySQL Server: Parser | Not a Bug (5978 days) | S3 | 5.0.37 | Linux (OpenSuse 10.2) | Any | subquery parsing with |
32146 | 2007-11-06 14:07 | 2008-01-08 19:39 | MySQL Server: Optimizer | No Feedback (5924 days) | S2 | 5.0.44 Gentoo Linux mysql-5.0.44 | Linux (Linux pavhome 2.6.22-gentoo-r8 #1 SMP Wed Oct 10 21:25:31 NOVST 2007 i686 Intel(R) Core(TM)2 CPU 660) | Any | Optimizer crushes under high load |
36259 | 2008-04-22 17:11 | 2011-02-16 23:43 | MySQL Server: Optimizer | Duplicate (5406 days) | S5 | 5.0.54, 5.1.23, 5.1.24, 5.1.25 | Windows | Any | Optimizing with ORDER BY |
37577 | 2008-06-23 6:40 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5055 days) | S5 | MySQL6.0 | Linux (SLES10SP1 (2.6.16.46-0.12-smp, x64)) | Any | Query Q9 of DBT3 is running on Falcon slower than Innodb |
Showing 1-30 of 140 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |