#65354Support for SPATIAL KEY in Schema / Migration
Description
Given the following definition in ext_tables.sql the Install Tool wants to re-create the index every time a database compare is being performed.
# # Table structure for tables 'tx_sitelist_domain_model_zipcode' # CREATE TABLE tx_spatial_domain_model_zipcode ( zipcode varchar(16) DEFAULT '' NOT NULL, place varchar(255) DEFAULT '' NOT NULL, location point DEFAULT '' NOT NULL, KEY zipcode (zipcode), SPATIAL KEY location (location) ) ENGINE=MyISAM;
1. An existing index is not being detected properly (wrong/unknown) type, this leads to being offered to drop existing index as well as creating the new index
2. Re-creating the index after database compare leads to duplicate index errors, it seems dropping the existing index would be performed after the new index has been created