Hi,
Checking the difference in sources from DB2_db and DB2_hash,
the only thing that changes is the DB_DUP flag... It seems to me that
it's a lot of complexity for no advantage. The idea was to have some
kind of 'abstract' database class. Unfortunately Database class is tightly
bound to the semantics of Berkeley DB and will never be good enough
for a SQL database (it would be good for gdbm/ndbm etc...).
I therefore propose to merge all that in the Database class.
That would simplify and speed up things a lot. I'm concerned about that
because modifying anything in the Database & DB2_db & DB2_hash requires
touching 6 files. I don't mind if we get an advantage. Since the advantage
we have is almost nothing, I'd say we should better go to the simpler
solution.
Thoughts ?
--
Loic Dachary
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 09 80, Fax: 33 1 56 96 09 61
e-mail: [EMAIL PROTECTED] URL: http://www.senga.org/
------------------------------------
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.
