[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFC: common database policy/infrastracture

> >     2. From the application point of view I could ask people to
> >        include an option which prevents the bootstrap script from
> >        doing the work which is just done.  I guess this is no big deal
> >        for the very responsive authors.
> i really think this would be ideal.  patching the already existing
> installer script to have a --noadmin option would then let the bulk
> of the work remain in the script (which gives you the benefit of
> still having something that works on non-debian systems),
AFACT right now I think we should already transparently be
able to do this (eg. test and use if exist, --noadmin not
necessary). Actually trying will likely turn up a bug or two
but we'll deal with that easily. Our current code is intended
to a) accept an existing database, b) accept not needing to
create the database user that will own the GnuMed database, c)
try to continue working in case we cannot become root and/or
postgres in order to do a) or b) -- which isn't necessary
if a) and b) are done by dbconfig-common already.

> On Fri, Dec 17, 2004 at 11:47:00AM +0100, Karsten Hilbert wrote:
> > > >but something to point out:  dbconfig-common already performs the
> > > >administrative actions needed to set up the database and database user
> > Well, see, the GnuMed bootstrapping does a lot more advanced
> > things regarding "the database user". There's users and groups
> > with varying levels of access to the database.
> are these actual mysql/pgsql database users,

> or users stored inside the gnumed database?

> currently, dbconfig-common doesn't do anything for the
> latter, and i don't know that it's a generalizable enough of a problem
> that it's worth trying.
I don't think so.

If dbconfig-common creates gm-dbowner (which is a database
owner intended to own all GnuMed database objects and which has
create-db and create-user rights) that would be enough. We
would then just rely on that and create "our" users/groups
under that account. dbconfig-common would just need to make
sure the "gnumed" database is created such that it is owned by

GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Reply to: