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:
None 
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

To submit contributions, please log in.