It is way past bed time so excuse me if I am way off...
What is the order of tables in the explain? What is shown as the select_type?
On 10/2/07, Eamon Daly [EMAIL PROTECTED] wrote:
Hi, all. I couldn't find this mentioned in the docs or in
the archives, so I'd figure I'd ask. I have a
After spending half the night trying this same query on a
number of different datasets, it looks like sometimes MySQL
/will/ use all parts in certain cases, so I'm satisfied by
that. Thanks for responding!
Eamon Daly
- Original
That probably means the optimizer is rejecting (part of) the index as
not selective enough to be efficient for the given query, depending on
storage engine index statistics.
Making sure your indexes are up to date can help on certain storage
engines (MyISAM). ANALYZE TABLE does this for you.
Hi, all. I couldn't find this mentioned in the docs or in
the archives, so I'd figure I'd ask. I have a table with a
multipart index on three columns. When querying the table
alone using IN operators on any of the three columns, all
parts of the index are used. However, if I do a JOIN with
another
