Re: Best index for searching on lat / long data i.e. decimal vs. float

2010-05-01 Thread dan
On Sat, 01 May 2010 15:28:46 -0500, mos wrote: > > SELECT * FROM `grid`� force index(section) WHERE n > 49.012 AND s < 49.012 > AND e > > 110.0244 AND w < 110.0244; > > It should give you the answer around 0.1 seconds. Give it a try. :-) > > Mike It actually makes it worse by ab

Re: Best index for searching on lat / long data i.e. decimal vs. float

2010-04-30 Thread dan
On Fri, 30 Apr 2010 17:14:06 -0500, mos wrote: > At 04:54 PM 4/30/2010, you wrote: > > Use Explain in front of your Select statement to see how many indexes it is mysql> explain SELECT * FROM `grid` WHERE n > 49.012 AND s < 49.012 AND e > 110.0244 AND w < 110.0244; ++-+-

Re: Best index for searching on lat / long data i.e. decimal vs. float

2010-04-30 Thread mos
At 04:54 PM 4/30/2010, you wrote: I have a table with over 8 million rows of lat / long data all currently in decimal(12,8) format (actually some in float(12,8)). First question - should I have these all in decimal or float? I can't think of any reason why I would actually do any math via mysq