[ Fix originally suggested by Robert Marchand ]
This patch fixes a problem introduced in 3.1.6's handling of date ranges
in htsearch, which was also in the 3.1.5 patches for this feature.
The test to see if the end date was set was wrong, so htsearch assumed
it always had to check the date for each match, which caused the extra
overhead described in http://www.htdig.org/FAQ.html#q5.10
Apply this patch in your main htdig-3.1.6 source directory using the
command: patch -p0 < this-message-file
--- htsearch/Display.cc.orig Thu Jan 31 17:47:18 2002
+++ htsearch/Display.cc Thu Feb 7 15:47:14 2002
@@ -1407,7 +1407,7 @@ Display::buildMatchList()
// New check added on whether or not we need to check date ranges - MG
if (date_factor != 0.0 || backlink_factor != 0.0 || typ != SortByScore
- || timet_startdate > 0 || enddate.tm_year < endoftime->tm_year)
+ || timet_startdate > 0 || timet_enddate < eternity)
{
DocumentRef *thisRef = docDB.FindCoded(thisMatch->getURL());
if (thisRef) // We better hope it's not null!
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
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
