Hi
i found a strange problem . when i using index for 'select' , i
got a slower result than without index .
i have a tabe :
create table geo_query (
`id` int(10) unsigned not null auto_increment ,
`start` bigint(20) unsigned not null ,
`end`
The optimizer is right, you are wrong, as simple as that :-)
value between [field1] and [field2] cannot use indices, as your primary
reference is a constant, not a field. Rewrite that to start = 1988778880 and
end = 1988778880 and the optimizer should pick up the index.
Index hints are rarely
[Note to self, reply to mailinglist, not to author ;) ]
i found a strange problem . when i using index for 'select' , i
got a slower result than without index .
i have a tabe :
create table geo_query (
`id` int(10) unsigned not null auto_increment ,
thanks . i dropped the primary key , and it still didn't use the index .
when i dropped the index `range`, and add two indexes `start` and
`end` . it picks up the index , but it still used more seconds than
using no
index with `start` and `end` indexed as one --`range`.
2011/7/28 Johan De
Dear MySQL users,
MySQL 5.5.15 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.15 is recommended
for use on production systems.
MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL
, version of virus signature
database 6333 (20110728) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
