On Wed, Feb 21, 2001 at 12:59:43PM +0000, Antony T Curtis wrote:
> In the case where there is a SELECT on a table where no index is
> directly applicable, if there is a compound index where the second part
> (or third, etc) of the index is used in the WHERE clause, it should be
> possible to still use that index by being able to skip rows rather than
> doing a brute-force search through all the records.
> Any hints where I should look to see if such an optimisation could be
It isn't clear to me how that would work. Do you mean, to scan
the whole index in order to find rows where the secondary index
part matches, instead of scanning the data file? Or do you have
something else in mind? I think this optimization wouldn't work,
but I'm not sure I understand what you're suggesting.
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Tim Smith <tim@stripped>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Development Team
/_/ /_/\_, /___/\___\_\___/ Boone, NC USA