|
Date: 11/29/2006 11:09 am · Subject: Re: Search not returning all results · Rating: 16
Did alot more digging and thinking. The problem here is not the stopwords mysql uses... searching for the word "getting" should'nt return any results as the word getting means nothing by it's self. The real issue here is knowing when mysql actually discards a word from the query because it's in the stopword list. I've dug and dug and can't find anyway to either: a) run a query after the match/against query to see if any stopwords were detected b) run a query against all current stopwords The list of default stopwords is listed in the docs, however it can be overriden from mysql server to mysql server. It is possible to detect if the default stopwords are being used... unfortunately 'default' can change from version to version of mysql which is impractical for us. So, at this point I have posted to the mysql forums to see what their take is. http://forums.mysql.com/read.php?107,128828,128828#msg-128828 If I get snake-eyes there, I think the best solution is something like this: 1 - Add a table to wG that contains the default mysql stopwords of current. 2 - Write a method that checks the query entered against the stopwords table after each search, and returns a list of words that were ignored. 3 - Add a config file parameter called 'StopwordsFile' or similar with a default value of 'built-in'. Our method could then run the query "show variables like 'ft_stopwords_file' and compare the result to the StopwordsFile config value to make sure they match. If they match, tell the user about words ignored, otherwise don't tell the user and write a warning to the log file that webgui doesn't know what stopwords are being used. I really hate that solution...
|
