[csw-maintainers] "package needs a database" general issue

[Philip Brown]

Hi folks,

There is an issue that comes up occasionally, where we want to offer an
'easy install' option for people for a particular package, but that package
requires a database to run.

Then there is a matter of; WHICH database should we use, for fully
automated install?!!

usually it comes down to a choice of "postgres or mysql?"

I would like to propose that we need to pick an official default database
to use.


Furthermore, I propose that that database be mysql. It's the simplest to
administer, it has the biggest mindshare, and there are lots of apps that
will ONLY support mysql, sadly.

HOWEVER, I always like to support end-user choice whenever possible.
So, in addition to a default assumption of mysql... I would also like to
propose a setting in csw.conf.
Something like

default_dbtype

where values can be mysql, postgres, or even oracle.
If that value is set, then a package can presume that that database is
already installed and running.
In those cases though, we also need to agree on some kind of common
mechanism to insert values into said database.

Comments?