[bravo_sierra]

Why in the world would you use this when MySQL has almost proper geospatial support? It's far more efficient and less incorrect.

I swear - next time I'm going to get a R-Tree novelty account.

[bad_user]

Because Mysql doesn't have support for distance searches.

[bravo_sierra]

Using the Buffer function it does. Then MySQL will utilize the geometry index, rather than scanning the table. Not clear in the docs, but it's there.

[bad_user]

Do you have an example?

[thibaut_barrere]

I'm interested as well (really, as someone who uses sphinx for that currently).

[bad_user]

Hey, I'm also using Sphinx :)

Also, thing is filtering is not much of a problem as you can use the Haversine formula ... it gets to be a problem if you also want sorting from closest to furthest.

[codesink]

geospatial index do NOT work if you're using InnoDB; so you must choose between geospatial queries or transactions (that MyISAM don't support).