| Showing 1-30 of 745 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 8113 | 2005-01-24 15:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5364 days) | S5 | 5.0, 5.1, azalea bzr | Any | Any | Select with between optimization |
| 8662 | 2005-02-21 21:31 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5260 days) | S5 | 6.0.14, 5.1.12-BK, 4.1.10 | Any | Any | optimizer, query takes 3 to 10 times as long when using index |
| 15907 | 2005-12-21 15:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5245 days) | S5 | 5.0.19-BK, 5.0.13, 6.0.14-bzr | Linux (Linux) | Any | Binary comparison ignores indexes |
| 17259 | 2006-02-09 2:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5652 days) | S5 | 5.0.15, 6.0.7 | Linux (Linux) | Any | Query optimizer chooses wrong index |
| 20111 | 2006-05-28 10:57 | 2014-01-24 13:26 | MySQL Server: Optimizer | Verified (3744 days) | S5 | 4.1.19-log | Linux (Linux) | Any | named columns used in subqueries hinder optimisation of LIKE, BETWEEN, range |
| 26832 | 2007-03-04 18:17 | 2011-04-05 14:46 | MySQL Server: Optimizer | Verified (4769 days) | S5 | 5.5 | Any | Any | ENUM types not optimized |
| 30342 | 2007-08-09 18:52 | 2015-10-07 14:54 | MySQL Server: Optimizer | Verified (3123 days) | S5 | 5.0.37, 5.6.17 | Any | Any | Equality propagation can make optimization much slower |
| 31446 | 2007-10-08 12:14 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5670 days) | S5 | 5.0.44, 5.0.37, 6.0.2 Alpha | Any | Any | Inefficient index use with order by and joins |
| 31901 | 2007-10-29 2:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5916 days) | S5 | 5.0.45 | Any | Any | read_rnd_buffer_size doesn't seem to be used as written in Reference Manual |
| 34310 | 2008-02-05 14:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (3781 days) | S5 | 5.0.51a-log, 5.0.54, 5.6.14 | Linux | Any | Optimizer is inefficient by using ORDER BY function() and LIMIT |
| 36817 | 2008-05-20 13:19 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5408 days) | S5 | 5.0.54a,5.1.19, 5.1.25, 5.0.60, 5.5 | Any | Any | Non optimal index choice, depending on index creation order |
| 37264 | 2008-06-07 22:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5670 days) | S5 | 5.1.24-rc 5.1.29-rc 5.1.30 | Any | Any | MySQL wrongly uses filesort |
| 38251 | 2008-07-21 0:29 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5757 days) | S5 | 5.0.51 | Any | Any | Useless external queries should be ignored |
| 38550 | 2008-08-04 21:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5670 days) | S5 | 5.0.60, 5.1 | Any | Any | multiple optimizer bugs for queries with references from preceding table |
| 41220 | 2008-12-04 9:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5364 days) | S5 | 5.1.30, 5.0, 5.1, azalea bzr | Any | Any | LEFT JOIN with compound clause uses table scan, while INNER JOIN uses indexes |
| 42808 | 2009-02-12 22:17 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5550 days) | S5 | 4.1, 5.0, 5.1 | Any | Any | Execution Plan Cache |
| 42948 | 2009-02-17 23:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5532 days) | S5 | 5.0.67-0ubuntu6, 6.0.11 | Linux (Ubuntu 8.10) | Any | MySQL Optimizer does not properly use Indexes on Views with "Group By" |
| 45776 | 2009-06-26 7:17 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5417 days) | S5 | mysql-5.1.35 | Linux | Any | "OR" condition on SPATIAL index not optimized |
| 46376 | 2009-07-24 17:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5384 days) | S5 | 5.0.85, 5.1.36, 5.1.38, 5.1.39 | Windows (XP) | Any | Optimizer choose wrong index even when where clause and order-by are covered |
| 46717 | 2009-08-14 11:14 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5358 days) | S5 | 5.1.32 | Any | Any | Unnecessary joins are not optimized away |
| 47330 | 2009-09-15 15:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5328 days) | S5 | 5.0.77, 5.1.34, 5.1.37 | Linux (Debian x64) | Any | Slow query with left join and having. |
| 48886 | 2009-11-19 0:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5271 days) | S5 | 5.1+ | Any | Any | MySQL doesn't seem to optimize "less than empty string" |
| 49276 | 2009-12-01 17:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5259 days) | S5 | 5.0.85-community-log, 5.0.89, 5.1.42 | Linux | Any | Optimization for IN (on InnoDB tables) depends on number of set elements |
| 50388 | 2010-01-16 4:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S5 | 5.1.41,5.1.42, 5.1.43-bzr | Any | Any | partition pruning not working with some right joins |
| 52029 | 2010-03-13 12:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5148 days) | S5 | 5.1.44 | Any | Any | GROUP BY results in much slower query |
| 52170 | 2010-03-18 9:57 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5148 days) | S5 | 5.1.44, mysql-next-mt | Linux (fc12) | Any | innodb query optimizer fails (null possible_keys) with multicolumn key |
| 52762 | 2010-04-12 10:49 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5126 days) | S5 | 5.3 | Any | Any | like should be index optimised if starts with _ rather than % |
| 55248 | 2010-07-14 9:22 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5034 days) | S5 | 5.1.43, 5.1.48 | Windows | Any | constant WHERE inefficient |
| 55979 | 2010-08-13 22:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5001 days) | S5 | 5.1.39 | Linux | Any | Key not used if IN() list contains mix of strings and integers |
| 58101 | 2010-11-10 0:21 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4914 days) | S5 | 5.1.38-community-log, 5.1.54-bzr | Linux | Any | Optimizer picks wrong order of queries |
| Showing 1-30 of 745 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
