Search Postgresql Archives

Re: chosing a database name

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

 



On Wed, Jul 13, 2005 at 01:21:01PM -0700, Philip Hallstrom wrote:

> >My main concern, however, was whether the *approach* is
> >sound, eg using a separate database name per release or IOW
> >version. One way would be to use the database name "gnumed"
> >regardless of release, another way would be to use
> >"gnumedX_Y" for release X.Y. I wonder whether the latter
> >approach has any drawbacks people might think of regarding
> >release management etc.
> 
> The only thing I can think is that if the changes from v1 to v2 don't 
> touch the schema, then you've got a lot of extra update-work to do that 
> really isn't necessary.
Got me !  :-)

> Doesn't hurt anything though and it gives you a 
> nice clean way of reverting back a version if necessary.
That's what I hope to achieve. Doesn't free me from backup
before upgrade but still.

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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
       message can get through to the mailing list cleanly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux