List:General Discussion« Previous MessageNext Message »
From:Christian Hammers Date:October 3 2006 9:54pm
Subject:Re: Glitch in Query Optimizer
View as plain text  
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.



Christian Hammers             WESTEND GmbH  |  Internet-Business-Provider
Technik                       CISCO Systems Partner - Authorized Reseller
                              Lütticher Straße 10      Tel 0241/701333-11
ch@stripped                D-52064 Aachen              Fax 0241/911879

Glitch in Query OptimizerRobert DiFalco3 Oct
  • RE: Glitch in Query OptimizerRobert DiFalco3 Oct
    • Re: RE: Glitch in Query OptimizerDan Buettner3 Oct
      • RE: RE: Glitch in Query OptimizerRobert DiFalco3 Oct
    • Re: Glitch in Query OptimizerChristian Hammers3 Oct
      • RE: Glitch in Query OptimizerRobert DiFalco4 Oct
        • Re: RE: Glitch in Query OptimizerDan Buettner4 Oct
  • Re: Glitch in Query OptimizerChris9 Oct
    • hello everyonealan10 Oct
      • Re: hello everyoneRolando Edwards10 Oct
    • hello everyonealan10 Oct
      • Re: hello everyonePeter Bradley10 Oct