Why do people want a SQL database. Is it because they want
to query the data in ways not yet available from HTdig.
Do they want dynamic access or just for statistics.
Could htdig produce an output file which would then be
able to seed a SQL as a batch job?
Currently HTdig builds out of the box.
To introduce a external dependency will
lead to version de-synchronisation.
> -----Original Message-----
> From: Geoff Hutchison [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, December 13, 1999 5:39 PM
> To: [EMAIL PROTECTED]
> Cc: Marc Britten; [EMAIL PROTECTED]
> Subject: Re: [htdig3-dev] Htdig database backend
>
> On Mon, 13 Dec 1999 [EMAIL PROTECTED] wrote:
>
> > old Berkeley DB files into SQL database. Trying to have a program able
> to
> > handle both will lead to *very* hairy code.
>
> Yes, it probably would be very hairy.
>
> Personally I worry about this. I think that while many people want to see
> a SQL backend, there shouldn't be a dependency on installing SQL. The
> Berkeley DB is fairly lightweight, installed on many systems already, and
> fairly robust.
>
> Yes, I agree that you don't want to emulate Berkely DB behavior with a SQL
> database. However, we have much of the code for advanced features like
> ANDs and ORs and LIKE in the code already. Moving to SQL would simplify
> it, but should we just throw out this code?
>
> (My answer would be "no, we should see what features from SQL we would
> *need* and think about how hard those would be for Berkeley DB with what
> we have now.")
>
> -Geoff Hutchison
> Williams Students Online
> http://wso.williams.edu/
>
>
> ------------------------------------
> To unsubscribe from the htdig3-dev mailing list, send a message to
> [EMAIL PROTECTED]
> You will receive a message to confirm this.
>
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
