DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=unCY9qCoqgmy8+4Sf8GdfcRFPWPkcFATXGlPTM0BrI24yoBta1Z7qwI412uvHJwHLEe0SHAeHG0ZCoBbny0sqxHyL/LJ5Iig5B2CWaKatr/wjbF6KpP4q1ygnHgr2tM6UwYbhL8auQC2NTjJLq1GozqSxZzIg896MBuoH/w5PIc=
Message-ID: <dcc563d10708010946o4c69542yc876c2bc16768e54@mail.gmail.com>
Date: Wed, 1 Aug 2007 11:46:11 -0500
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "John Mitchell" <mitchelljj98@gmail.com>
Subject: Re: How do I connect postgres table structures and view structures to
	an existing svn repository?
Cc: "D'Arcy J.M. Cain" <darcy@druid.net>, pgsql-sql@postgresql.org
In-Reply-To: <fa2ac0580708010845r9108596r14ec88ae4420ce11@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fa2ac0580708010707n488b1906rf74d487de801673f@mail.gmail.com>
	<20070801113812.6a2d6fac.darcy@druid.net>
	<fa2ac0580708010845r9108596r14ec88ae4420ce11@mail.gmail.com>

On 8/1/07, John Mitchell <mitchelljj98@gmail.com> wrote:
> I am trying to store schema definitions in version-control which I can do by
> saving the definition and then  importing  into svn, but I  would like  it
> to be automatic , so that when an update occurs to a table or view within
> postgres then that table or view is flagged within svn.  This would be
> similar to what I currently do with source code that I have for a web app
> within  eclipse.

OK, the first decision point is whether you want to store whole
schemas and blow away the old one each time, or if you want to store
incremental changes.

I recommend creating an initial schema of version 1.0, and then
creating delta files after that as you change your schema.

Your first schema can have a table in it called schemaversion(version
text primary key, notes text); with an entry there something like
'1.0','initial schema'.

Each delta .sql file you create would then have an insert into the
schemaversion table with the version number it brings the schema up to
and a note of possibly the change ticket or bug number or even a brief
overview of the changes it implements.

That way you can have a production schema at some stable version, say
1.0.8, while your development schema can move ahead to 2.0.4.  then
you can simply apply the delta files to take you from 1.0.8 to 2.0.4
when you want to upgrade production.

Store each of these files in some directory in svn and you're done.

My point being that you need to drive the changes from the svn side,
not the database side.  I've seen no reliable way to do it otherwise,
but would love to be pleasantly surprised.