next question is how to deal with backwards compat? should there be two
sets of the DB calls in the source with and IFDEF around them? or two
sets of files, the right one gets moved into place during ./configure?
already have plans to do a DB abstraction layer, does anyone thing that
the current berkely stuff could be made compatible? i'm afraid I don't
know much about their stuff
[EMAIL PROTECTED] wrote:
>
> Marc Britten writes:
> > hello all,
> >
> > I'm looking into moving the Berkely DB backend to a DBMS system(probably
> > MySQL to begin with)
> >
> > any comments/tips?
>
> If you're diving into that make sure you write a class that wraps mysql
> specifics so that postgres and others can be added at a later time. A good
> source of inspiration for the interface is Perl DBI module.
> There is a class system that does it for mysql (libmysql++ I think, on
> mysql.com) but it's far too heavy (uses templates).
> Also be prepared to change a lot of things in htdig since the semantics
> of an SQL database are *very* different from the semantics of Berkeley DB.
> This is a major change and I strongly think it's very impractical to keep
> both systems in the same code (Berkeley DB + SQL).
>
> Cheers,
>
> --
> Loic Dachary
>
> ECILA
> 100 av. du Gal Leclerc
> 93500 Pantin - France
> Tel: 33 1 56 96 10 85
> e-mail: [EMAIL PROTECTED]
> URL: http://www.senga.org/
>
> ------------------------------------
> 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.
