On Fri, Dec 12, 2008 at 1:51 PM, Thom Brown <thombrown@xxxxxxxxx> wrote: > What about managing the script files themselves, keeping in mind that some > scripts could be applied to more than one database version, like a database > which is a branched version of another database, but which have common > elements which can both be updated by a common script. Although sometimes a > script would be unique to that database. I'd use a branched svn / cvs type setup. And upgrade scripts that take you from branch to another (or trunk to a new branch, whichever you'd be doing.) -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
