Re: Function tracking

From: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
To: Rebecca Clarke <r(dot)clarke83(at)gmail(dot)com>
Cc: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Function tracking
Date: 2013-06-07 15:44:57
Message-ID: CAB8KJ=jsNEFXX9k8UND0ikcNGTg=0=5C7aorsQEGx10L3MpRDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2013/6/7 Rebecca Clarke <r(dot)clarke83(at)gmail(dot)com>:
> Hi all
>
> 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).

You might want to take a look at Sqitch ( http://sqitch.org/ ), which
is a little
complex to set up, but works along similar lines to GIT.

As others have said, you definitely need to use some kind of source control
to track changes. With the systems I've managed, I've ensured that releases
are tagged in the source control system with a release number, and that
database script files exist for each release (if needed) which are applied
when the release is rolled out to the respective environment. It's still a bit
of a manual process and requires a bit of (self) discipline, but has worked
quite well for me.

Regards

Ian Barwick

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2013-06-07 15:52:59 Re: Function tracking
Previous Message Stephen Cook 2013-06-07 15:24:05 Re: Function tracking