Noise "chars"

Hi all,
I have this strange behaviour with fulltext search: I have a keywords field
which is used for full text indexing.
In one row I have the keyword 'geography' (without ', of course). If I
search with:

CONTAINSTABLE (phe_keywords, *, '+geography+')
CONTAINSTABLE (phe_keywords, *, '<geography>')
CONTAINSTABLE (phe_keywords, *, '-geography-')

I always get the same row as result, which is not what I expected to have.
I looked at noiseENG.txt file, but these chars are not in the list (only $
appears in the list).

So my question is: how do I specify full text not to ignore these chars in
full text search?

Many thanks.

-f

Fabio wrote on Wed, 27 Feb 2008 11:13:43 +0100:

> Hi all,
> I have this strange behaviour with fulltext search: I have a keywords
> field which is used for full text indexing.
> In one row I have the keyword 'geography' (without ', of course). If I
> search with:

> CONTAINSTABLE (phe_keywords, *, '+geography+')
> CONTAINSTABLE (phe_keywords, *, '<geography>')
> CONTAINSTABLE (phe_keywords, *, '-geography-')

> I always get the same row as result, which is not what I expected to
> have.
> I looked at noiseENG.txt file, but these chars are not in the list
> (only $ appears in the list).

> So my question is: how do I specify full text not to ignore these chars
> in full text search?

You can't - they are treated as "word breakers", and so are effectively
discarded from the search as white space.

--
Dan