mysql查询地理位置,数据库：查询地理位置数据的最佳性能方式？

I have a MySQL database. I store homes in the database and perform literally just 1 query against the database, but I need this query to be performed super fast, and that's to return all homes within a square box geo latitude & longitude.

SELECT * FROM homes

WHERE geolat BETWEEN ??? AND ???

AND geolng BETWEEN ??? AND ???

How is the best way for me to store my geo data so that I can perform this query of displaying all home within the geolocation box the quickest?

Basically:

Am I using the best SQL statement to perform this query the quickest?

Does any other method exist, maybe not even using a database, for me to query the fastest way a result of homes within a boxed geolocation bounds?

In case it helps, I've include my database table schema below:

CREATE TABLE IF NOT EXISTS `homes` (

`home_id` int(10) unsigned NOT NULL auto_increment,

`address` varchar(128) collate utf8_unicode_ci NOT NULL,

`city` varchar(64) collate utf8_unicode_ci NOT NULL,

`state` varchar(2) collate utf8_unicode_ci NOT NULL,

`zip` mediumint(8) unsigned NOT NULL,

`price` mediumint(8) unsigned NOT NULL,

`sqft` smallint(5) unsigned NOT NULL,

`year_built` smallint(5) unsigned NOT NULL,

`geolat` decimal(10,6) default NULL,

`geolng` decimal(10,6) default NULL,

PRIMARY KEY (`home_id`),

KEY `geolat` (`geolat`),

KEY `geolng` (`geolng`),

) ENGINE=InnoDB ;

UPDATE

I understand spatial will factor in the curvature of the earth but I'm most interested in returning geo data the FASTEST. Unless these spatial database packages somehow return data faster, please don't recommend spatial extensions. Thanks

UPDATE 2

Please note, no one below has truly answered the question. I'm really looking forward to any assistance I might receive. Thanks in advance.

解决方案

There is a good paper on MySQL geolocation performance here.

EDIT Pretty sure this is using fixed radius. Also I am not 100% certain the algorithm for calculating distance is the most advanced (i.e. it'll "drill" through Earth).

What's significant is that the algorithm is cheap to give you a ball park limit on the number of rows to do proper distance search.