I asked about this a week ago when I was considering implimenting it. The
answer I was given was that to simply drop in a sql backend that kept the
same interface as the current db was a bad design idea because DB2 doesnt'
support many of the sql command easily.
My thoughts to that are we could start with a work-alike sql backend, and
then start to abstract things so that the sql specific queries are
generated within sql_db.cc or whatever and the DB2 can ignore them or
whatever seems apropriate. I wouldn't expect to be able to switch from one
to the other on the fly without redigging.
I started looking at the code about a week and a half ago which is too
short of a time to become an expert, so if people with replies could point
out a file or section of a file it would help.
-james
------------------------------------
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.
