Bug #42295 compatibility - engines and indexes
Submitted: 23 Jan 2009 9:51 Modified: 12 Jul 2013 14:54
Reporter: Kolarov Yavor Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.29 OS:Any
Assigned to: CPU Architecture:Any
Tags: engine, GUI, INDEX

[23 Jan 2009 9:51] Kolarov Yavor 
Description:
Hello,

Firstly I would like to thank you for Workbench! It is a really nice and usefull tool!

Here comes the requested feature: I have just designed a DB with Geodata. In order to improve the performance I created a spatial index for one of the columns, saved, exported a sql script and executed it. I was surprised that it failed with an error message. 

After 15 minitues searching on the net I found the reason: InnoDB does not support spatial indexing. I fixed it by changing the engine.

How to repeat:
Just create a table with an incompatible index and engine combination. You are free to store and export.

Suggested fix:
It would be nice if MySQL Workbench could detect such incompatibilities and react. I would expect it to at least suggest/indicate the incompatibility.
[23 Jan 2009 10:06] Valeriy Kravchuk 
Thank you for a reasonable feature request.
[12 Jul 2013 14:54] Alfredo Kojima 
Duplicate of bug #31939