Search Postgresql Archives

Re: How to store version number of database layout

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

 



> It's more like a question of best practice:
> How do you managing different version of database layout for e.g.
> software releases?
> We are planing to do an application based on postgres and want to store
> some version number of database layout to ensure correct upgrade-scripts
> can be applied in case of an upgrade. Is there any build in for?

We (www.gnumed.de) generate the md5 of a concatenation of the database
layout (tables/columns/PKs) which the client checks against and disconnects
if there's a mismatch.

Karsten


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[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