TorgoX noted that one of his journals was not showing up in the fulltext journal search by the term "obviously". Hm. After some searching br Krow, it is discovered that MySQL 3.x has a stopword list compiled in if COMPILE_STOPWORDS_IN is defined, and obviously is a stopword. Yow. We can edit the list, undef the COMPILE_STOPWORDS_IN, or not use that word anymore!
Yikes (Score:1)
Other words that MySQL thinks we'll never need to search for include "unfortunately", "willing", "afterwards" (but not "afterward"?), "corresponding", "associated", "known", "second", "unlikely", "better", and "immediate". It seems like a pretty random selection.
Re:Yikes (Score:1)
Re:Yikes (Score:1)
The specific problem that caused me to delve into the list of stop words in the other search software was that people were unable to search for the cigarette brand More (this was a database of tobacco company documents released as a result of court orders) because "more" was a stop word.
I guess that's a good reason not to n
Re:Yikes (Score:1)
Re:Yikes (Score:1)
By the way, the username and the word "Journal" (but not, for some reason, the "'s") in the heading have been white in light mode for a few weeks, which makes them invisible with normal settings. Probably something that got changed around
Re:Yikes (Score:2)
Obviously bingo (Score:1)