At 12:47 PM +0200 4/13/00, Geschke Steffen wrote:
>Since v3.2.0b2 the option "wordlist_compress" is set true by default.
>However, htsearch and htdump doesn't work correctly with a
>compressed database (at least for a standard configuration).
>
>If the search is successful, the matching score is always 1%.
>
>The $(MODIFIED) variable doesn't work in output templates
>(for both, beta 1 and 2), although document list (printed
>by htdump) contains 'm:' values for all documents.
OK, I can reproduce both of these behaviors on my copy of 3.2.0b2 as
well. I guess I should have actually flipped through the results, not
just seen that there were the right number. :-(
First off, I would like to know if others are seeing the same thing.
It's an easy bug to reproduce--take a look at the htsearch output.
I first thought the score problems might have something to do with my
changes to the scoring system. But even taking this portion of code
out or bumping up the scoring _factor attributes doesn't help.
My biggest concern is that the modified date shouldn't have anything
to do with the word database. So why does it matter if the word DB is
compressed?
I probably won't have time to do a thorough debugging of this for a
while and it may take a few sets of eyes to work it out. So any help
in this would be greatly appreciated.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
