I have a column in a table that is configured for full text searching.
I can search the DB with this:


SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
('"add"' IN BOOLEAN MODE);


It will not return results when searching for the work "add" or ("Add"
or any other variant). It can find phases that include the word "add"
like this:

SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
('"add to base"' IN BOOLEAN MODE);

That works fine. It can also find records with any other single word
that I've tested. I'm using the command line interface in Linux and
using the Query Browser Client in windows with the same results. Any
idea what's going on here? What am I missing?

Bruce wrote:
> I have a column in a table that is configured for full text searching.
> I can search the DB with this:
>
>
> SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
> ('"add"' IN BOOLEAN MODE);
>
>
> It will not return results when searching for the work "add" or ("Add"
> or any other variant). It can find phases that include the word "add"
> like this:
>
> SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
> ('"add to base"' IN BOOLEAN MODE);
>
> That works fine. It can also find records with any other single word
> that I've tested. I'm using the command line interface in Linux and
> using the Query Browser Client in windows with the same results. Any
> idea what's going on here? What am I missing?

You're missing that bit where you read the manual and it says:
"The default minimum value is four characters;"

Yep, I missed that. Thanks.



Paul Lautman wrote:
> Bruce wrote:
> > I have a column in a table that is configured for full text searching.
> > I can search the DB with this:
> >
> >
> > SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
> > ('"add"' IN BOOLEAN MODE);
> >
> >
> > It will not return results when searching for the work "add" or ("Add"
> > or any other variant). It can find phases that include the word "add"
> > like this:
> >
> > SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
> > ('"add to base"' IN BOOLEAN MODE);
> >
> > That works fine. It can also find records with any other single word
> > that I've tested. I'm using the command line interface in Linux and
> > using the Query Browser Client in windows with the same results. Any
> > idea what's going on here? What am I missing?
>
> You're missing that bit where you read the manual and it says:
> "The default minimum value is four characters;"

Bruce wrote:
> Yep, I missed that. Thanks.
>
>
>
> Paul Lautman wrote:
>> Bruce wrote:
>>> I have a column in a table that is configured for full text
>>> searching. I can search the DB with this:
>>>
>>>
>>> SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
>>> ('"add"' IN BOOLEAN MODE);
>>>
>>>
>>> It will not return results when searching for the work "add" or
>>> ("Add" or any other variant). It can find phases that include the
>>> word "add" like this:
>>>
>>> SELECT * FROM mydb.MyTable where MATCH (strFullTextColumn) AGAINST
>>> ('"add to base"' IN BOOLEAN MODE);
>>>
>>> That works fine. It can also find records with any other single word
>>> that I've tested. I'm using the command line interface in Linux and
>>> using the Query Browser Client in windows with the same results.
>>> Any idea what's going on here? What am I missing?
>>
>> You're missing that bit where you read the manual and it says:
>> "The default minimum value is four characters;"

Be sure and read the next bit that says that you can change this value.

I changed the variable and it worked. Thanks for you help!