Menu

#1553 (ok 4.4) Error #1795 - InnoDB presently supports one FULLTEXT index creation at a time

Next_release
fixed
None
Low
2015-04-20
2014-10-23
No

While exporting structure of table with few FULLTEXT indexes PhpMyAdmin exports all indexes together, namely:

ALTER TABLE table_name ADD FULLTEXT KEY text1 (text1), ADD FULLTEXT KEY text2 (text2);

And because of this on import you'll get:

#1795 - InnoDB presently supports one FULLTEXT index creation at a time

That is why PhpMyAdmin at export should separate creation of FULLTEXT indexes into few SQL commands.

Discussion

  • Madhura Jayaratne

    • assigned_to: Madhura Jayaratne
     
  • Marc Delisle

    Marc Delisle - 2014-11-23
    • summary: #1795 - InnoDB presently supports one FULLTEXT index creation at a time --> (ok 4.4) Error #1795 - InnoDB presently supports one FULLTEXT index creation at a time
    • status: open --> resolved
    • Group: Needs_decision --> Next_release
    • Priority: 5 --> 1
     
  • Marc Delisle

    Marc Delisle - 2015-04-20
    • Status: resolved --> fixed
     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.