Andrew Scherpbier writes:
> I don't like the idea of having the whole configuration set in a sql
> database. It makes it hard to deal with when no sql is available. (We still
> want to allow ht://Dig to be used *without* external database tools) It also
> makes it almost manditory to create tools to maintain the configuration. A
> simple text based configuration file like what exists now should be used at
> all times.
I agree this is a major drawback. The SQL table could be optional as
far as configuration is concerned. I.e. if you want to deal with the
table only, go ahead but be prepared to need HTML SQL interface and
all that stuff. If you don't want to deal with table, then use
the file. Internal routines of htdig would always manipulate the
table. If the configuration file is available then it *always*
override the table. If it is not available use what's already in the
table.
For SQL database usage in general, I'm sure htdig would benefit a lot
(speed, maintainablity, versatility) if an SQL database was used to store
the document database for instance. Just try to add a new field in the
document database if you're not convinced. It's a two steps process with
an SQL database.
> However, I think it is a great idea to allow values to be located in a sql
> database. As you know, the current configuration file allows for the
> expansion of a whole file as an attribute value. We can easily extend that
> sort of mechanism to include other data sources.
That would be very nice indeed. And we are back to XML that provides a
syntax to specify external data sources for inclusion.
> Proost,
Firztz,
--
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.
