Bug #80779

SQL-ERROR: The used table type doesn't support FULLTEXT indexes

Added by Christian Toffolo about 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Install Tool
Start date:
2017-04-10
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Executing 'Update database schema: Create tables and fields'
returns:
SQL-ERROR: The used table type doesn't support FULLTEXT indexes

Problem 1.
It doesn't state which query caused the problem.

Problem 2.
The query is 'ALTER TABLE index_fulltext ENGINE = InnoDB'
there's an error because before MySQL 5.6 Full-Text Search is supported only with MyISAM Engine.

History

#1 Updated by Morton Jonuschat about 2 years ago

  • Status changed from New to Needs Feedback

Are there other tables/field which should be modified on this table? It seems like it tries to downgrade the index_fulltext table from MySQL FULLTEXT to the database agnostic setup. Did you disable the config option 'useMysqlFulltext' for indexed_search or is this an upgrade from an installation that previously used indexed_search_mysql?

#2 Updated by Christian Toffolo about 2 years ago

It's an upgrade from 7LTS to 8LTS.
The installation previously used EXT:indexed_search_mysql.
Now I checked EXT:indexed_search config and the flag basic.useMysqlFulltext is not set.

Btw, I temporarly solved the problem 2 dropping the table and recreating it with:

CREATE TABLE index_fulltext (
  phash int(11) DEFAULT '0' NOT NULL,
  fulltextdata mediumtext,
  metaphonedata mediumtext NOT NULL,
  PRIMARY KEY (phash)
) ENGINE=InnoDB;

#3 Updated by Benni Mack about 2 years ago

  • Target version changed from 8 LTS to Candidate for patchlevel

#4 Updated by Alexander Opitz almost 2 years ago

  • Status changed from Needs Feedback to New

Also available in: Atom PDF