On Tue, 14 Dec 1999, Geoff Hutchison wrote:
> On Tue, 14 Dec 1999, Bill Carlson wrote:
>
> > Manipulate until I get what I want, then dump to htdig databases. It seems
> > that a lot of people spend a lot of time getting htdig to index only what
> > they want where they could spend very little time massaging the data in
> > another tool.
> >
> > Again, I think the primary reason for a SQL backend is data access, not
> > performance.
>
> In that case, would a set of tools for accessing the Berkely DB be
> suitable? Let's say we provide a bunch of tools for dumping the databases
> to an ASCII form, then re-loading them. Would this be sufficient for your
> purposes?
>
For my particular purposes, that would be great. And as I said, I think
this is the main reason many people have requested the move to a SQL
backend. Look at how often the question of the contrib perl scripts not
working pops up on the htdig list, people want to do interesting things
with the htdig data other than just searching.
To me, it doesn't matter what the backend is if I have the tools to get
data to and from the backend.
I imagine there are some valid requests for SQL that relate to
performance, but I think the real solution there is to throw hardware at
HTDig. You can't expect to index the Internet on a Pentium class machine.
:)
Bill Carlson
------------
Systems Programmer [EMAIL PROTECTED] | Opinions are mine,
Virtual Hospital http://www.vh.org/ | not my employer's.
University of Iowa Hospitals and Clinics |
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
