| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Function tracking |
| Date: | 2013-06-07 15:52:59 |
| Message-ID: | kosvkk$q8o$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rebecca Clarke wrote on 07.06.2013 12:30:
> I'm looking for suggestions on the best way to track the updates to a
> function.
>
> We have two databases, Dev & Live, so I want to update Live with just
> the functions that have been modified in the DEV databas3e. Is there
> another, easier way to track the updates than manually recording it
> in a document? (I'm trying to eliminate human interference).
We are pretty happy using Liquibase for all our schema migrations.
For stored procedures/functions it's best to use a changeSet that includes a SQL file
and is marked as runOnChange=true
The Liquibase changelog files are then stored in Subversion.
A little shell script applies the changes to any environment we want
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | François Beausoleil | 2013-06-07 16:00:52 | Re: Slave promotion failure |
| Previous Message | Ian Lawrence Barwick | 2013-06-07 15:44:57 | Re: Function tracking |