Wikka Mod 023
Type: Feature AdditionCredit:
???? - For originally coding the categories action.- The original idea for a (much simpler) category action seems to have come from Michael Abendroth (IbuKi) on the page IbukiCategoryAction @ WakkaWiki. -- JavaWoman
Added function FullCategoryTextSearch to wakka.php because I found out that MySQL was not returning the expected category results.
The search result is empty because the word MySQL is present in at least 50% of the rows. As such, it is effectively treated as a stopword. For large datasets, this is the most desirable behavior--a natural language query should not return every second row from a 1GB table. For small datasets, it may be less desirable.
A word that matches half of rows in a table is less likely to locate relevant documents. In fact, it will most likely find plenty of irrelevant documents. We all know this happens far too often when we are trying to find something on the Internet with a search engine. It is with this reasoning that rows containing the word are assigned a low semantic value for the particular dataset in which they occur. A given word may exceed the 50% threshold in one dataset but not another.
The 50% threshold has a significant implication when you first try full-text searching to see how it works: If you create a table and insert only one or two rows of text into it, every word in the text occurs in at least 50% of the rows. As a result, no searches return any results. Be sure to insert at least three rows, and preferably many more.
function FullCategoryTextSearch($phrase) { return $this->LoadAll("select * from ".$this->config["table_prefix"]."pages where latest = 'Y' and match(tag, body) against('".mysql_escape_string($phrase)."' IN BOOLEAN MODE)"); }
and - of course - it would be helpful to have a more detailed description of your problem. eventually it will bring you closer to a quick fix.