Bug in forum search with "value"

[kh99]

From the mysql manual:

The default stopword list is given in Section 11.8.4, “Full-Text Stopwords”. The default minimum word length and stopword list can be changed as described in Section 11.8.6, “Fine-Tuning MySQL Full-Text Search”.

So maybe a fix can be found on this page: http://dev.mysql.com/doc/refman/5.4/...ne-tuning.html

I agree that it's strange that "value" is on that list of words.

[Oz81]

Thanks, you're a genius, indeed! This must be the source for the mistake but it looks like I would need to recompile MySQL to effectively change the stopwords list!?

I cannot do this on my system, unfortunately, so the mistake stays unsolved. :|
Oh no, I'm wrong maybe it works without, I'll try it later ...

[kh99]

No, a genius would have posted that back in post #3...

[Oz81]

Damn MySQL, the current version of stopwords is built-in on my system:
ft stopword file (built-in)

So, no chance to change this without recompiling. :|
But at least now we know why it doesn't work ...

[Lynne]

You don't need to recompile:

After changing the value of this variable or the contents of the stopword file, restart the server and rebuild your FULLTEXT indexes.

[Oz81]

Okay, please tell my how I can change the contents of a built-in stopword file without recompiling.

[Lynne]

OK, admittedly, I've never done this, but I can read the page that on the mysql site. It says:

To override the default stopword list, set the ft_stopword_file system variable. (See Section 5.1.4, “Server System Variables”.) The variable value should be the path name of the file containing the stopword list, or the empty string to disable stopword filtering. After changing the value of this variable or the contents of the stopword file, restart the server and rebuild your FULLTEXT indexes.

You can set the variable either while the system is running (I think just SET xxxxx, I can't remember exactly) or in the my.cnf file. Then restart. I don't see where you are seeing anything about recompiling.

[kh99]

Is it possible that "built-in" means that it's using the default set, and to customize it you are meant to replace "built-in" with the name of a file?

ETA: OK, it looks like to change it you can put this in the my.ini file:

[mysqld]
ft_stopword_file=""

(or put a file name in the quotes if you want to provide an alternate list of words).

I haven't tried to see how it affects searches but it changes what is reported as the value of that variable. I guess the next question is how you go about rebuilding the indexes.

ETA: I tried it on my Windows system at home, maybe it's different on a Linux server.

[Oz81]

Oh no, I totally misunderstood "built-in", you're right.
I put "ft_stopword_file = ''" into my.cnf and it seems to work though it's not quite easy to rebuild the index on a huge MySQL table.
But I'll manage this somehow later. Thanks a lot for your help, you made my day!

[kh99]

You probably realize this already, but just as a reminder: if you use an alternate list or no list in MySQL, you might want to change that searchwords.php to reflect it so that users will get the correct message.

In retrospect, probably the reason you were so confused is because if a search word appears in the searchwords.php file, the user will get a message that says "The following words are either very common, too long, or too short and were not included in your search :". But since your vbulletin had a list of German words, you probably never saw that message.