[htdig-dev] Re: htsearch 3.2 rejects records with modtime of 0?

[Lachlan A. <lh...@us...>]

Greetings Gilles,

In  htcommon/defaults.cc,  startyear  is specified as 1970, so your=20
config file would have to explicitly clear  startyear  to say no date=20
is given.

The reason for  startyear  being specified in  defaults.cc  is that=20
the default value should be in  attrs.html,  which is automatically=20
generated.  The three fixes I can think of (in order of my=20
preference) are:

1. Set the (hard-coded) default value of  startday  in
   htsearch/Display.cc to 0 instead of 1. I'm not sure if this would
   work, and it may break other things.
2. Leave  startyear  empty in defaults.cc and manually hack attrs.hml.
3. Leave  startyear  undocumented.

Opinions?

Cheers,
Lachlan

On Wed, 22 Oct 2003 08:30, Gilles Detillieux wrote:
> even
> though these dozen or so web pages were definitely in the database,
> and came out into db.docs after an htdump (with a m:0 field),
> htsearch would not show these in search results.  I looked at the
> code, and the only thing that I can see that would cause this is if
> the startyear, startmonth or startday input parameters were set,
> causing the timet_startdate value in Display.cc to be greater than
> 0.  But I didn't set these!  I ran htsearch from the command line,
> so I know I wasn't passing it these values as input parameters, and
> the config file I used didn't define these as attributes either.

--=20
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)