[ic] mv_exact_match not working

[interchange-users@icdevgroup.org (Webpraxis Consulting Ltd.)]

At 07:00 PM 11/6/02 -0800, you wrote:
>>    I am experiencing an issue identical to what is described in this
>>message:
>>
>>http://www.icdevgroup.org/pipermail/interchange-users/2002-February
>>/017481.h
>>tml
>>
>>    which is where s search using "em" is returning nonexact matches, ie a
>>search for "shaving" will return "shaving" and "shaving cream".  The
>>workaround described in the message (co=1, os=1) works.  What I am confused
>>by is the patch described in the message.  The context doesn't match my
>>4.8.6 Server.pm close enough for me to even hand patch it.  I was wondering
>>if this was a 4.9.x patch or if there was something I was missing.
>>
>>
>>Thanks,
>>Jeff
>
>I have the same problem.  Does 4.9 fix this?
>
>- Grant

Hi Jeff & Grant,
The purpose of the search option 'em' is to either enable (em=0) or disable
(em=1) word parsing of the search text. Thus, all things being defaulted,
it corresponds to partially matching any entry with "shaving" or "cream" as
keywords versus "shaving cream" respectively.

However, if I understand you guys correctly, what you really want here is
"op=eq". This imposes equality between the search text and a db text field
thereby making "shaving" and "shaving cream" distinct results.

I too was mislead by the option's name my first time around. I now think of
it as the searchspec parsing option.

Hope this helps,
Yves

Yves Beaudoin, Ph.D., President,
Webpraxis Consulting Ltd.,
Edmonton, Alberta, Canada, T5R 5S5
E-mail: post@webpraxis.ab.ca

Owner of the Virtual Railroad:
www.webpraxis.ab.ca/vrr/