[Dbconfig-common-devel] Questions about upgrading

[Karsten Hilbert]

On Sat, Jul 08, 2006 at 05:54:19PM -0400, sean finney wrote:

> > As far as I can tell, dbconfig couples the upgrade of the packages
> > database with the upgrade of the package.  I wonder if that's the best
> > choice.  Many packages can support multiple database instances, so it
> 
> yes, it's by design this way.  this way if something goes wrong,
> the admin knows about it immediately, and has a chance to fix things
> (there's also an option to ignore the problem and fix it later).
> 
> since dbconfig-common doesn't currently support multi-instance
> databases, i'm not too concerned on how it handles an upgrade
> for a multi-instance database.  that is, if someone's in that situation,
> they've already >= some of the setup manually, so they can do >= some
> of the upgrade manually too.
> 
> that said, one of the things on my TODO is multi-instance support...

Well, I wonder whether supporting *that* notion of
multi-instance is the job of db-common-config ?

After all, if a package supports multiple database instances
in, say, different database engines and/or even in different
versions then it should really provide:

 gnumed-server-pgsql-0.1.deb
 gnumed-server-mysql-0.1.deb
 gnumed-server-pgsql-0.2.deb

Then

 gnumed-server-pgsql.deb
 gnumed-server-mysql.deb

would point to the latest version that would be installed by

 apt-get upgrade

Upgrades from, say, 0.1 to 0.2 would require 0.1 to be
installed and then

 apt-get install gnumed-server-pgsql-0.2.deb

which should detect the 0.1 instance and ask whether to
upgrade that one or install a new 0.2 one unless 0.2 is
already installed.

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