MySQL Forums
Forum List  »  Optimizer & Parser

"cases for which the optimizer puts the table in the wrong order"
Posted by: mathieu
Date: June 23, 2005 07:00AM

Hi,

I'm currently working on how to improve execution's time of few queries ; and so I find out the "STRAIGHT_JOIN" statement in mysql documentation.

The documentations says that this is useful in case "the optimizer puts the table in the wrong order".

Do you have any example of cases in which this happens ?

Btw, forcing mysql to read the table in a defined order requires to have an idea of which order is the best. Is there an order that is usually better (for example, from the smaller table to the bigger) , or does it completely depend on the tables ?

Options: ReplyQuote


Subject
Views
Written By
Posted
"cases for which the optimizer puts the table in the wrong order"
2907
June 23, 2005 07:00AM


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.