Hi,
Gilles Detillieux wrote:
> consideration. Big fields like DocHead should not need to be fetched when
> all you want are small fields to help with scoring and sorting, such as the
> backlink count, time, and perhaps the title. These should be in separate
> records, or even separate files.
I'm quite ignorant on the point of the various unix db libraries. So
correct me if I'm wrong..
I mostly have a SQL database background and what you say here sounds
just like standard SQL
functionality (I refer to just getting a small number of fields from a
table). But switching
to SQL would also bring some of the quirks of SQL in the house.
I know too little of the internal db stuff of htdig. But in general one
would do in SQL something
like create one or more tables with all the info you want.
For instance:
DocID Url Date ... ... ...
The db.docurl db from Plan 1 could then be made by creating a index one
the URL field. Limiting
the search to stuff within a certain time frame would become something
of
SELECT <a fieldlist> FROM docdb WHERE Date BETWEEN x AND y
Thus giving only the desired fields.
Again.. just a few thoughts...
Ric
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
