Fulltext index: cannot be created because the max message length is above 65,53

[Mike Bobbitt]

I've done the InnoDB conversion listed here and now I get the following message in red on my search settings screen:

Code Select Expand

Fulltext index:  cannot be created because the max message length is above 65,53

I'd like to use a fulltext index, but am not able to at the moment. Any advice on how to do this?


Thanks
Mike

[Compuart]

Did you convert the messages table to InnoDB too?

[Mike Bobbitt]

Nope, messages is still MyISAM, I've only converted the tables listed in the reference post above.

[Ben_S]

Is your messages body column a mediumtext field?

[Mike Bobbitt]

It's a plain "text" field (presumably larger than mediumtext).

Thanks all.

[Ben_S]

Odd, text is what it should be. Mediumtext is actually larger. The max size for  text is 65535 chars so I'm not sure how your getting that message. Perhaps Compuart might have an idea.

[Mike Bobbitt]

I've also confirmed that the max post length is 25000, so that should be OK...

[Compuart]

It might be a problem with the collation of the body column. Have to dive into that deeper though.

Which version of MySQL are you using btw?

[Mike Bobbitt]

Ah yeah, that's probably it. I'm using utf8_general_ci which has caused some problems. I'm considering switching to latin1, but am afraid of what it might do!

[Compuart]

You could try to create the index manually, I think that'll work:

Code Select Expand

ALTER TABLE smf_messages
ADD FULLTEXT body (body)

I'll look into a fix for the code later.

[Mike Bobbitt]

Thanks, that did it!