CODEWITHSUNDEEP
mysqlsql
Saurabh
Saurabh

Reputation: 163

Order of execution in MySQL query with multiple JOINS of subqueries

I have the following query with a LEFT JOIN between the first two subqueries e and a, and an INNER JOIN between the last two subqueries a and m:

SELECT {cols}
FROM 
(SELECT {cols}
 FROM {table} 
 WHERE {conditions}) AS e
LEFT JOIN
(SELECT {cols}
 FROM {table} 
 WHERE {conditions}) AS a
ON e.col = a.col
INNER JOIN
(SELECT {cols}
 FROM {table} 
 WHERE {conditions}) AS m
ON e.col = m.col

When I change the second join from INNER JOIN to LEFT JOIN, the execution time increase by a factor of ~200. The number of records from each subquery is as follows:

e -> Number of records: 303
a -> Number of records: 18
m -> Number of recordings: 295

I assumed MySQL would evaluate each subquery as an independent subquery and then do the joins, in which case, the change from INNER JOIN to LEFT JOIN should not lead to such an increase in the execution time given the relatively low number of records as shown above.

So, obviously it seems that's not the execution order being followed.

EXPLAIN PLAN:

Case 1 with INNER JOIN: join e with m first, then join with a. 
Case 2 with LEFT JOIN: join e with a first, then join with m.

I'm not sure why the two plans are different in the two cases and how this might lead to a difference in the execution time.

Can anyone help explain to me what the actual execution order may be?

Upvotes: 0

Views: 737

Answers (1)

Gordan Bobić
Gordan Bobić

Reputation: 1878

The join order is up to the query planner to optimize as it sees fit. Sometimes it gets it wrong. If you think the join order is suboptimal you can force it by specifying SELECT STRAIGHT_JOIN instead of SELECT. This will force the query planner to join tables in the order listed in the query.

Outer joins are always going to be slower because they have to scan more rows - they cannot discard rows that don't match in both sides.

Upvotes: 1

Related Questions