Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

[Solved] Broken Search? : The used table type doesn't support FULLTEXT*

edited October 2011 in Vanilla 2.0 - 2.8
I'm trying to search the forums ... but cannot, I'm getting a server error about the column not supporting that search. Any ideas?


  • The error is:

    The used table type doesn't support FULLTEXT indexes|Gdn_Database|Query|select * from ( select match(d.Name, d.Body) against(:Search0) as `Relavence`, d.DiscussionID as `PrimaryID`, d.Name as `Title`, d.Body as `Summary`, d.Format as `Format`, d.CategoryID as `CategoryID`, concat('/discussion/', d.DiscussionID) as `Url`, d.DateInserted as `DateInserted`, d.InsertUserID as `UserID` from GDN_Discussion d where d.CategoryID in (-1, 9, 23, 26, 24, 27) and match(d.Name, d.Body) against (:Search1) union all select match(c.Body) against(:Search2) as `Relavence`, c.CommentID as `PrimaryID`, d.Name as `Title`, c.Body as `Summary`, c.Format as `Format`, d.CategoryID as `CategoryID`, concat('/discussion/comment/', c.CommentID, '/#Comment_', c.CommentID) as `Url`, c.DateInserted as `DateInserted`, c.InsertUserID as `UserID` from GDN_Comment c join GDN_Discussion d on d.DiscussionID = c.DiscussionID where d.CategoryID in ('-1', '9', '23', '26', '24', '27') and match(c.Body) against (:Search3) ) s order by s.DateInserted desc limit 20
  • Focus on this error message: The used table type doesn't support FULLTEXT

    There was an error rendering this rich post.

  • x00x00 MVP
    edited October 2011
    @UnderDog no offence but you come across as patronising and don't always know what you are talking about.

    He was talking about, the problem appears to to be solved.

    grep is your friend.

  • jspautschjspautsch Themester ✭✭✭
    He was talking about
    Could've fooled me, it wasn't exactly clear.

  • It was there in his opening statement, and that was the case.

    grep is your friend.

Sign In or Register to comment.