James O'Kane wrote:
>
> Hi,
> I've looked over the mailing lists archive and I see several
> mentionings of the desire for an sql backend, but I never see anyone who
> has actually put anything together. Someone on cosource.com
> (http://www.cosource.com/cgi-bin/cos.pl/wish/info/162) is trying to
> sponsor the work, so I thought I would look into coding it. I've looked
> over the code and it seems that what I would need to do is impliment the
> same public functions as DB2_db.h/.cc and add some configuration options?
> Is there anything else that I've missed?
It is not quite that easy ;-)
To have a good working SQL database backend, you should not adopt
the techniques used for DB2/DBM. The main differences are in the
connection to the database backend (there is no database file, but
a database server) and in the database structure.
>From my point of view, a proper SQL backend needs a rewrite of the
non-SQL code (to get a portable interface to non-SQL databases),
i.e. a new high-level interface that matches the special needs and
features of both, SQL and non-SQL databases. Many things currently
done by Ht://Dig itself could then (whenever SQL is used as a backend)
be transferred to the SQL server.
cheers,
Torsten
--
InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH
Waldhofstra�e 14 Tel: +49-4101-403605
D-25474 Ellerbek Fax: +49-4101-403606
E-Mail: [EMAIL PROTECTED] Internet: http://www.inwise.de
------------------------------------
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.
