Bryan Montgomery wrote on 01.06.2012 17:28:
So we've been reviewing our processes and working on improving them. One area we've been lacking is a procedure to version control our database functions, table changes, static data etc. I'm curious how others do it. Ideally, we want it to be part of our release / build process so that we deploy functions. However, how do you handle dependancies? We've also used patch files if we need to modify tables - these are typically written to only run once, ie alter table add column x int. Any thoughts on putting this in to a process so that it can be run mutliple times without any issue?
We have quite good experience with Liquibase to manage the DB scripts Regards Thomas -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
