Workaround for setting ft_min_word_len global variable?
Posted by:
James H
Date: March 11, 2009 06:00AM
Hiya,
I have asked my MySQL host to change the ft_min_word_len setting in the option file, but they won't do it as it's a shared environment, etc.
The reason I want it changing it because (with ft_min_word_len currently set to 4), queries such as
...WHERE (MATCH(name) AGAINST('tr-24' IN BOOLEAN MODE) return no results. (The hyphen does not seem to be the sole cause of the problem as using 'tr-3451' does yield results.)
Is there a workaround for not being able to set ft_min_word_len? (The only idea I came across was changing out the -'s in the db records to _'s and changing the query to ...WHERE (MATCH(name) AGAINST('tr_24' IN BOOLEAN MODE) but this is far from ideal.)
Cheers,
James
Subject
Views
Written By
Posted
Workaround for setting ft_min_word_len global variable?
7764
March 11, 2009 06:00AM
3977
May 19, 2009 03:34AM
Sorry, you can't reply to this topic. It has been closed.
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.