From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Question: How do you manage version control? |
Date: | 2012-06-01 15:51:35 |
Message-ID: | jqaoe4$et6$1@dough.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Ralf Schuchardt | 2012-06-01 16:23:58 | Re: Question: How do you manage version control? |
Previous Message | Chris Angelico | 2012-06-01 15:48:44 | Re: Question: How do you manage version control? |