Bug #53495 InnoDB does not support spatial (rtree-) Indexes
Submitted: 7 May 2010 15:33 Modified: 7 May 2010 15:57
Reporter: Lenz Grimmer Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version:Any OS:Any
Assigned to: CPU Architecture:Any
Tags: gis, INDEX, innodb, rtree, spatial

[7 May 2010 15:33] Lenz Grimmer 
Description:
Currently, only MyISAM support SPATIAL indexes (aka R-Tree Indexes). While InnoDB is capable of storing spatial data, it's currently not possible to effectively perorm spatial queries on this information. This is a request to add support for spatial indexes to InnoDB.

How to repeat:
Store spatial data in an InnoDB table. Observe that it's not possible to create a SPATIAL index on this table.

Suggested fix:
Implement rtree-Indexes in InnoDB
[7 May 2010 15:57] Valeriy Kravchuk 
Thank you for the feature request.
[20 Jan 2011 22:19] Adam Nelson 
Any progress on this?  We're falling behind Postgres big time with this issue alone.  Everybody's going geo and this is a dealbreaker for alot of other developers.
[16 Feb 2011 11:52] Mathias Walter 
Why can't this feature just merged from the MyISAM system? Is it because of the clustered primary index?
[10 Jul 2012 0:57] Greg Hazel 
Another +1. I'm switching to PostGIS for now, until MySQL gains support for this on InnoDB.