Issue Bug Closed

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

Christian Toffolo 04/10/17, 11:17 updated 01/23/24, 11:46

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.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 5

  1. Morton Jonuschat commented and changed status New Needs Feedback 04/15/17, 19:42

    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. Christian Toffolo commented 04/19/17, 08:27

    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. Benni Mack changed target version 05/04/17, 17:48

  4. Alexander Opitz changed status Needs Feedback New 08/28/17, 10:56

  5. Christian Kuhn commented and changed status New Closed 01/23/24, 11:46

    Hey. I’m going to close here: Whatever went wrong on this 7 years ago, core v12 requires at least mysql 8, which comes with innodb fulltext support.