Bug #23536 Documentation claims InnoDB supports spatial extensions
Submitted: 22 Oct 2006 23:10 Modified: 29 Nov 2006 17:43
Reporter: Ask Hansen (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0 OS:
Assigned to: MC Brown CPU Architecture:Any
Tags: documentation, innodb, spatial

[22 Oct 2006 23:10] Ask Hansen
Description:

says

As of MySQL 5.0.16, InnoDB, NDB, BDB, and ARCHIVE also support spatial features. (However, the ARCHIVE engine does not support indexing, so spatial columns in ARCHIVE columns cannot be indexed. [...]

and "Although spatial extensions are supported in InnoDB tables, use of spatial indexes may cause a crash. (Bug#15860)"

Rather than getting the crash fixed, spatial indexes were disabled for InnoDB tables.  

How to repeat:
Read http://dev.mysql.com/doc/refman/5.0/en/spatial-extensions.html

Suggested fix:
The documentation should be updated.
[22 Oct 2006 23:12] Ask Hansen
see also http://bugs.mysql.com/18929
[22 Oct 2006 23:27] Hartmut Holzgraefe
spatial indexes were never implemented for InnoDB,
the crash was not fixed by disabling them, it was 
caused due to trying to use something that wasn't 
there in the first place ...
[13 Nov 2006 23:54] Ask Hansen
Hartmut,

What are you talking about?   My bug report is that _your documentation says it *currently works*_.  The documentation also says that it "may cause crashes".

As a response to your incorrect assertion that "it was caused due to trying to use something that wasn't 
there in the first place" - It was announced as a new feature of 5.0.16.

http://dev.mysql.com/doc/refman/5.0/en/news-5-0-16.html

"The InnoDB, NDB, BDB, and ARCHIVE storage engines now support spatial columns. See Chapter 16, Spatial Extensions."

Please don't repond to bug reports if you don't want to bother researching them first.
[14 Nov 2006 20:51] Sveta Smirnova
Thank you for the report.

Verified as described.
[29 Nov 2006 17:43] MC Brown
The documentation has been updated with a warning that spatial indexes are not supported for the InnoDB, Archive and NDB engines.