Bug #30264 | Two BETWEENs not using a composite index optimally - could be 3200x faster | ||
---|---|---|---|
Submitted: | 7 Aug 2007 3:30 | Modified: | 7 Aug 2007 23:19 |
Reporter: | Tasman Hayes | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S4 (Feature request) |
Version: | 5.1.20 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | between, composite index, index range scan, two betweens |
[7 Aug 2007 3:30]
Tasman Hayes
[7 Aug 2007 4:29]
Valeriy Kravchuk
Thank you for a problem report. It looks like a reasonable feature request for me. But it is not a bug, formally, as execution path you proposed is not described in the manual (and I do not know any RDBMS where it is implemented).
[7 Aug 2007 23:19]
Tasman Hayes
Thank you for analyzing & responding to my report so quickly. Thank you also for leaving my report in place as a feature request. Much appreciated. Does MySQL AB have a process in place for escalating feature requests? Having this execution path in MySQL would dramatically increase our application performance. Thank you again!
[7 Aug 2007 23:19]
Tasman Hayes
Thank you for analyzing & responding to my report so quickly. Thank you also for leaving my report in place as a feature request. Much appreciated. Does MySQL AB have a process in place for escalating feature requests? Having this execution path in MySQL would dramatically increase our application performance. Thank you again!
[25 Nov 2019 4:17]
WANG GUANGYOU
I think it is difficult to implement this