Re: 2 column between optimization
Posted by:
Jay Pipes
Date: September 06, 2005 09:22PM
Well, it's doing a full table scan of 2M rows... The reason it is doing this is because more than ~35% of the values in the GeoFeatureLocationBoundingBox index fall between 1 and 2. In order to get the index to be used, you will need to supply more stringent criteria.
BTW, KimSeong Loh's comments made absolute sense when he wrote them. From your query in the first post, it looked like you were issuing an impossible query against an INT field. Since you did not supply the table schema, we wouldn't know if the field values *could* fall between 1 and 2...
Jay Pipes
Community Relations Manager, North America, MySQL Inc.
Got Cluster?
http://www.mysql.com/cluster
Personal:
http://jpipes.com
Subject
Views
Written By
Posted
6441
September 02, 2005 12:39PM
3028
September 02, 2005 02:01PM
3290
September 02, 2005 02:25PM
2994
September 02, 2005 03:38PM
2849
September 06, 2005 09:17PM
2859
September 05, 2005 12:03PM
2926
September 06, 2005 09:18PM
2844
September 04, 2005 07:21PM
2845
September 06, 2005 09:14PM
Re: 2 column between optimization
3084
September 06, 2005 09:22PM
2849
September 06, 2005 11:17PM
2790
September 07, 2005 02:54AM
3164
September 07, 2005 02:48AM
2943
September 07, 2005 12:25PM
2756
September 07, 2005 12:54PM
Sorry, you can't reply to this topic. It has been closed.
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.
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.