[TYPO3-dev] faults in table-creation for index_fulltext and index_words

Dmitry Dulepov dmitry at typo3.org
Wed Oct 6 12:17:58 CEST 2010


Hi!

David Bruchmann wrote:
> for the tables  index_fulltext and index_words there is a FULLTEXT
> defined but FULLTEXT exists only for MyIsam-Tables and the tables are
> InnoDB.

There is no FYULLTEXT there. Here is from the ext_tables.sql:

#
# Table structure for table 'index_fulltext'
#
CREATE TABLE index_fulltext (
  phash int(11) DEFAULT '0' NOT NULL,
  fulltextdata mediumtext,
  PRIMARY KEY (phash)
) ENGINE=InnoDB;

#
# Table structure for table 'index_words'
#
CREATE TABLE index_words (
  wid int(11) DEFAULT '0' NOT NULL,
  baseword varchar(60) DEFAULT '' NOT NULL,
  metaphone int(11) DEFAULT '0' NOT NULL,
  is_stopword tinyint(3) DEFAULT '0' NOT NULL,
  PRIMARY KEY (wid),
  KEY baseword (baseword,wid),
  KEY metaphone (metaphone,wid)
) ENGINE=InnoDB;

> Is it better now to change to MyIsam or to run them without FULLTEXT?

No. InnoDb there is for performance reasons. Taking it out will block all
visits to page when indexed search updates indexes.

-- 
Dmitry Dulepov
TYPO3 core&security team member
Twitter: http://twitter.com/dmitryd
Read more @ http://dmitry-dulepov.com/




More information about the TYPO3-dev mailing list