fulltext
| Project: | SQL Search (Trip Search) |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I am trying to use the trip_search module using Drupal 5.6, PHP 5.2.1 and Mysql 5.0.37.
When I enable the module I get this errors:
# user warning: The used table type doesn't support FULLTEXT indexes query: CREATE FULLTEXT INDEX node_ft ON node (title) in [...]\includes\database.mysql.inc on line 172.
# user warning: The used table type doesn't support FULLTEXT indexes query: CREATE FULLTEXT INDEX term_ft ON term_data (name,description) in [...]\includes\database.mysql.inc on line 172.
# user warning: The used table type doesn't support FULLTEXT indexes query: CREATE FULLTEXT INDEX noderev_ft ON node_revisions (body) in [..]\includes\database.mysql.inc on line 172.
# user warning: The used table type doesn't support FULLTEXT indexes query: CREATE FULLTEXT INDEX comment_ft ON comments (subject,comment) in [...]\includes\database.mysql.inc on line 172
Then, each time I try to search, I receive again similar errors (user warning: The used table type doesn't support FULLTEXT indexes query: SELECT DISTINCT(t.tid), t.name, t.description FROM term_data t WHERE MATCH (t.name,t.description) AGAINST ('+a ' IN BOOLEAN MODE) LIMIT 0, 500 in [...]\includes\database.mysql.inc on line 172.
I fixed the problem - on my website - using manually an "alter table xx engine=MyIsam" on tables: node, node_revisions, term_data and comments and now it works. Just I wonder if it's a correct way to solve the problem, or if you can suggest something better?
thanks

#1
I'am with the same problem !! Please someone help us.
#2
Your tables are probably of the InnoDB type, which does not support FULLTEXT indexing (check out the table type in PHPMyAdmin). This module only works with MyISAM tables. It is possible to convert tables from InnoDB to MyISAM, but it's not trivial and might cause unpleasant side effects.