Re: Glitch in Query Optimizer

[Christian Hammers]

On Tue, Oct 03, 2006 at 01:35:01PM -0700, Robert DiFalco wrote:
> Scratch that, the only way to have the optimizer "choose" the correct
> index is to remove all compound indices that start with "NodeID" or move
> NodeID so that it is not the first column specified in the compound
> index. Ugh. Any ideas?

Search the docs for "FORCE INDEX ()" and "IGNORE INDEX ()" if you don't
want to rely on MySQL's cleverness.

bye,

-christian-

-- 
Christian Hammers             WESTEND GmbH  |  Internet-Business-Provider
Technik                       CISCO Systems Partner - Authorized Reseller
                              Lütticher Straße 10      Tel [phone]
ch@stripped                D-52064 Aachen              Fax [phone]