Bug #6713 The used table type doesn't support FULLTEXT indexes

Submitted: 19 Nov 2004 2:18 Modified: 13 Nov 2010 22:13
Reporter: Jesus Christ Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S2 (Serious)
Version:Newest OS:Windows (XP)
Assigned to: CPU Architecture:Any

[19 Nov 2004 2:18] Jesus Christ
Description:
Error 
SQL-query: 

ALTER TABLE ibf_posts ADD FULLTEXT (

post
) 
MySQL said:  

#1214 - The used table type doesn't support FULLTEXT indexes 

How to repeat:
Try installing IPB boards ^.^

Suggested fix:
Don't have one.
Wish to god I did.
[19 Nov 2004 6:19] MySQL Verification Team
Hi,

Full-text search is supported only on MyISAM table type. What is the type of  ibf_posts table?
[14 Feb 2005 22:54] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[16 Nov 2007 21:16] Galicia Badillo
ALTER TABLE my_table ENGINE = MYISAM;

Do this before the FullText add, even if the engine database default is already MyISAM
[31 Aug 2008 13:39] Nadeem Akram
Goto /your_ipb_directory/install/sql/mysql_fulltext.php

and instead of:
<?php
$INDEX[] = "alter table ibf_posts ADD FULLTEXT(post)";
$INDEX[] = "alter table ibf_topics ADD FULLTEXT(title)";
?>

change it to:
<?php
$INDEX[] = "ALTER TABLE ibf_posts ENGINE = MYISAM";
$INDEX[] = "ALTER TABLE ibf_topics ENGINE = MYISAM";
$INDEX[] = "alter table ibf_posts ADD FULLTEXT(post)";
$INDEX[] = "alter table ibf_topics ADD FULLTEXT(title)";

?>
and it will install perfectly fine :)
IPB v2.0.0 btw
[11 Nov 2010 2:30] Peter Petrov
This is NOT a bug in MySQL! Just lack of knowledge of the guy that reported it.

To install IP.Board, you HAVE to use MyISAM, not InnoDB!

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.