Re: Query using "ref" instead of "range" access
Hi Rick,
The approximate times are:
My first query (join): 7 sec
My revised query (stored procedure): 2 sec
Your query (subquery): 7.5 sec
By the way, I found this quote from Sergey Petrunya in
http://bugs.mysql.com/bug.php?id=38550 :
Quote
No, at the moment range scan may not depend on another table (with exception
of references to constant tables which are constidered constants). It seems
you're asking about combining ref and range access together. We have this on
somewhere our todo but I can't tell when this will become available.
It seems like what I what isn't implemented, so a workaround like my stored procedure may be the best option for now.
Subject
Views
Written By
Posted
4178
July 09, 2009 04:52PM
1937
July 11, 2009 09:57PM
Re: Query using "ref" instead of "range" access
2165
July 11, 2009 10:59PM
2084
July 12, 2009 09:32AM
1994
July 14, 2009 04:37PM
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.