Posted by denisb on 06/19/07 09:07

lawrence k <lkrubner@geocities.com> wrote:
> Wierd. Go to this page:
> http://www.ihanuman.com/search.php
> and search for "yoga"
> This query gets run:
> SELECT * FROM albums WHERE MATCH(name,description) AGAINST ('yoga')
> ORDER BY id DESC
> it returns nothing. (other searches work, but not the one for
> "yoga").
> But if I do SELECT * FROM albums WHERE description LIKE '%yoga%'
> then I get 5 matches
> What the hell??

hello,

<cit>
The search result is empty because the word ['yoga'] 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.
</cit>

in : http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html

--
@@@@@
E -00 comme on est very beaux dis !
' `) /
|\_ =="

• Next in forum: Re: test mail() on development machine w/o smtp server
• Prev in forum: Re: problem with functions and paths
• Thread view: Re: why does MATCH/AGAINST fail to catch entries that LIKE does catch?

[Reply to this message]