Project

General

Profile

Actions

Bug #65354

closed

Support for SPATIAL KEY in Schema / Migration

Added by Morton Jonuschat over 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2015-02-26
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #67217: Install-Tool Upgrade Wizard chokes on unknown index typesClosed2015-06-01

Actions
Actions

Also available in: Atom PDF