NOT searches descrepancy

skalyanaraman · Post by **skalyanaraman** » Wed Dec 17, 2003 5:10 pm

Hi,
we have the latest version and we have a record with the following info in it:

FIELD1
'Lucas, George'; Harrison Ford

If we try to search as,

FIELD1 NOT like 'Lucas' and FIELD1 like 'Harrison'

we get the above record as hit.
Even
FIELD1 NOT like 'Lucas'

gives the above record as hit.

We have the field fully indexed and the _T and _D files are 62bytes. so, they are in sync.

Could you please help us?

thanks

Post by **mark** » Wed Dec 17, 2003 6:02 pm

What are your index expressions?

skalyanaraman · Post by **skalyanaraman** » Wed Dec 17, 2003 6:06 pm

This is what we add before every create index statement.

set delexp=0;set addexp='\alnum{1,99}';set addexp='>>\alpha{1,50},=\alpha{1,50}'

Thanks!!

Post by **mark** » Thu Dec 18, 2003 12:17 pm

Remove ' from wordc at query time:
<SQL "set wordc='[\alpha]'"></SQL>

skalyanaraman · Post by **skalyanaraman** » Thu Dec 18, 2003 3:26 pm

We have the app which allows users to type in or choose the operator that they want to search on.
making wordc only alphabet is hard for us, just at query time.
Unless, this is a universal solution.
i.e. we take single quote out of the wordc for all searches.

Why taking ' out of wordc fix this anyway?
why only for NOT?

TIA

Post by **mark** » Thu Dec 18, 2003 6:01 pm

Take ' out universally. It causes a slight inconsistency between index and linear search. NOT like does a linear search. You just won't be able to use possessives in the query such as "myron's" but you can still use "myron" to find the "myron" part of "myron's" in the text.