[Dbconfig-common-devel] Re: new mailing list for db apps [was: Re: RFC: common database policy/infrastracture]

[Andreas Tille]

On Tue, 21 Dec 2004, Karsten Hilbert wrote:

>> so, i think what would work best would be to
>> give you the means to grant those extra privileges easily.
> Well, no. IMO dbconfig-common would need to be postgres, create
> the user "gm-dbowner", grant create-db and create-user to
> gm-dbowner, and create the database "gnumed" such that it
> belongs to gm-dbowner. Only *then* it should run the
> bootstrapping script provided by GnuMed ...
I think I will go definitely this way.  The question is whether this
kind of feature is necessary for dbconfig-common.  It might be some
special thing and perhaps overkill for our common framework in the
first place.  On the other hand it might be quite handy for others
to notice this feature, because I think it is a quite secure way to
handle data bases.

>> okay, i think i understand where you're coming from now.  i think this
>> is slightly different in the mysql world; i don't think you can have
>> that level of granularity on users at least.
> Well... There's a reason we use PostgreSQL ;-)
:)

>> should be a problem.  the trickiest part would be the cleanup process
>> in removing the package, which might need to take care of the
>> extra users/dbs that it created.
> I think cleanup should just run the cleanup SQL provided by
> GnuMed (doesn't exist yet), then remove the database gnumed,
> then remove the database user gm-dbowner.
Just for my personal understanding.  Do we need an extra cleanup script in
addition to removing the whole databae?

> Agree. Please put me on it or tell me where to go to
> subscribe.
    http://lists.alioth.debian.org/mailman/listinfo/dbconfig-common-devel

Kind regards

         Andreas.

-- 
http://fam-tille.de