On Sunday, October 20, 2002, at 07:45 PM, Patterson, Andrew wrote:

The symptoms of the problem are a worse than I originally described. All of
the following phrase searches:
"and testing"
"or testing"
"testing and"
"testing and something"
"testing not something"

Resulted in an internal server error being reported (after the browser sat
there doing nothing for quite a while). This only happened when using the
phrases with a method of "boolean" (the search methods "or" and "and" work
fine).
I didn't ever see the internal server error, but I was probably just too impatient. With the boolean method, there was certainly no response within what I would consider a reasonable amount of time. The results I mentioned in my last message corresponded to queries that did not use the boolean method. Although the problem associated with the boolean method of course needs to be addressed, I am not sure that I understand why you are using it in this case. An 'and' or 'or' as part of a quoted string is not treated as a boolean operator, regardless of what method you use.

Also, the phrase "or testing" failed as well, "or" is not set in my
bad_words file. The phrase "from testing" and "find from testing" worked
alright ("from" is in my bad_words file).
It is likely that 'or' is treated in much the same way as words in the bad_words file. It is less than the default minimum length and therefore not indexed (unless you changed the minimum_word_length attribute).

I will try and update to a more current version and check if I still have
this problem.
I am able to duplicate all of the problems you are encountering with the Oct. 13 snapshot.

Jim



-------------------------------------------------------
This sf.net email is sponsored by:
Access Your PC Securely with GoToMyPC. Try Free Now
https://www.gotomypc.com/s/OSND/DD
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html


Reply via email to