First, what version of swishe are you using? What OS? What compiler
was used to build swishe?
Have you tried rebuilding the index? Do you get the exact same results?
Since I can't reproduce the problem (and know one else has reported
that they can reproduce it either) you will have to help by performing
Create an index with only a few of the "science" and "technology"
files in it. Be sure to include some of the files that match each of
the "or" expressions (ie: matches "a or b" but not "b or a", matches both,
matches "b or a" but not "a or b"). Do you get the same results
when searching this smaller index? If so then it might be possible to
someone else to use those files to debug the problem on another system.
At 01:15 PM 3/11/99 -0500, rl wrote:
>I think the "or" thing is a real problem... but how would we figure out
>what's going on so whomever is developing the system can look into it?
>At 08:34 AM 3/10/99 -0500, Mark Gaulin wrote:
>>That definitely does not sound right, but I am unable to reproduce
>>it on my index. For your second, more complex query, what
>>happens if you use ()'s to group it like this:
>>(science or technology) and metaone=this and (metatwo=this or metatwo=that)
>>Also note that you need to add the second "metatwo=" for the "that".
>>At 11:29 PM 3/9/99 -0800, you wrote:
>>>I've been having some problems with "or" in queries.
>>>If I do a query for "science or technology" in my index, I get (say) 32
>>>hits, but if I do a search for "technology or science", I then get another
>>>number (say) 53 hits. This should never happen, right?
>>>Also, if I have a complex query using metatags like
>>> science or technology and metaone=this and metatwo=this or that
>>>this also doesn't work (no results, when I definitely should have some),
>>>but if I do either:
>>> science or technology and metaone=this and metatwo=this
>>> science or technology and metaone=this and metatwo=that
>>>I do get results.
>>>I think this is a genuine bug... any idea what's going on?
Received on Thu Mar 11 13:28:30 1999