MySQL Forums
Forum List  »  General

Re: Optimised way to search over 2 milllion poi data in mysql
Posted by: newbie Shai
Date: September 06, 2014 10:18PM

Dear Rick,
So I just maintain this is it ADD PRIMARY KEY (`poiID`), ADD KEY `lat` (`lat`,`long`)? Why would this two be not helpful ADD KEY `lat_2` (`lat`), ADD KEY `long` (`long`); because we search them where lat = ? and long = ? So you mean to say based on my table size of 2 Million data it will take up 200Mb of space. But the problem is that we have many lat long to be match to find nearest poi. This the problem where I want to avoid full table scan which I find useless? Any idea to optimize on that based on my table size and structure ?

About your two table I think I get it now. The first table you just purely store lat and long nothing else. The second one you store exactly same with first but plus location name and other details am I right?

Options: ReplyQuote


Subject
Written By
Posted
Re: Optimised way to search over 2 milllion poi data in mysql
September 06, 2014 10:18PM


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.