Re: Sorting over multiple JOINS
Posted by:
Rick James
Date: January 21, 2015 02:14PM
A cross-table JOIN is essentially unoptimizable (except in the non-defunct Akiban engine).
INDEX (thingID , info1)
is backwards. You need info1 to be first in order to be more efficient with the WHERE clause.
Please provide the EXPLAIN SELECT of the query that is taking so long. There may be some additional clues. (And it would be handy to have the actual SHOW CREATE TABLE and SELECT. Again, there can be subtle things going on that your summary failed to capture.)
Subject
Written By
Posted
Re: Sorting over multiple JOINS
January 21, 2015 02:14PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.