Bug #13317 | VIEW doesn't use index | ||
---|---|---|---|
Submitted: | 19 Sep 2005 10:11 | Modified: | 28 Sep 2005 1:59 |
Reporter: | Georg Richter | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
Version: | 5.0.14 | OS: | Linux (SLES 9) |
Assigned to: | Sergey Petrunya | CPU Architecture: | Any |
[19 Sep 2005 10:11]
Georg Richter
[20 Sep 2005 22:04]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/30124
[21 Sep 2005 17:33]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/30165
[24 Sep 2005 23:14]
Sergey Petrunya
Fix pushed into 5.0.14 tree. Bug description for the changelog: In queries over VIEWs that are processed using MERGE algorithm, range optimizer was unable to create ranges for "view.col IN (<constants>)" or "view.col BETWEEN const1 AND const2". This limitation is now removed.
[28 Sep 2005 1:59]
Mike Hillyer
Added to 5.0.14 functionality change list: <listitem> <para> Range scans can now be performed for queries on VIEWs such as <literal>column IN (<constants>)</literal> and <literal>column BETWEEN ConstantA AND ConstantB</literal>. (Bug #13317) </para> </listitem>