Hi Joyce,
"needs" is a stopword, that's why it's not indexed or found. You can
use your own ft_stopword_file to define the list without "needs." The
default, built-in stopword list is defined in, I think, the
myisam/ft_static.c file of the source distribution, for reference.
Hope that helps.
Matt
----- Original Message -----
From: <[EMAIL PROTECTED]>
Sent: Wednesday, April 28, 2004 12:01 AM
Subject: fulltext index -- word "needs" not found
> >Description:
> We have three different unrelated tables, each with one field that
> has a fulltext index. In each table, in the field with the fulltext
> index, there are records with the word "needs" in them, and in each
case no
> records are found when doing this type of query (using a fulltext
index):
>
> select * from testdb where match(highergeog) against('needs' in
boolean mode);
>
> However, records are found when doing substring searches:
>
> select * from testdb where highergeog like '%needs%';
>
<snip>
>
> Also I know someone running 4.0.15 on linux, and "needs" can't be
found
> in fulltext queries on his data also, even though the word exists in
the data.
>
> Perhaps this is all solved in 4.0.18?
>
>
> >Fix:
> Don't use fulltext index--use substring search.
> But substring is slower than fulltext.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
