On Tue, 7 Dec 1999, Marc Britten wrote:
> create new Database and DB2_db classes, use old code at reference of
> course
I'm sure others will have comments. You might want to check back in the
list archive <http://www.htdig.org/htdig3-dev/> since we had a discussion
on this about a month ago, if memory serves.
(And if you don't already know about it, there's an active request at
cosource.com for this very thing.)
> and thats about it, out side of making sure that all of the major
> components compile fine after changes
The biggest problem is that the current Database class is really tied to
the Berkeley DB. Granted, it doesn't use the Berkeley join() function, but
it certainly doesn't allow the kinds of queries that SQL supports. So it's
not clear how you'd want to bridge the gap.
> one question is what are the DB layouts? the compiled text isn't too
> readable to the human eye. also CreateSearchDB, would this be needed if
> proper indexing was done?
Ignore the DocumentDB class. IMHO it should be a level above any database
class. (This may be difficult, but there needs to be an abstraction layer
and I think this class makes as much sense as any other.) For the document
db, the fields are outlined in DocumentRef.h. I'd have to poke around in
htword/* to find the current word database structure, but Loic is the
expert there now.
As for CreateSearchDB()? Yes, you're right, it's left over from past
versions. So it will probably be moving out of DocumentDB and into a new
tool soon.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
