Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id A4B0B9FB1F9 for ; Wed, 1 Aug 2007 15:17:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 81993-01 for ; Wed, 1 Aug 2007 15:17:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from smaug.vex.net (smaug.vex.net [208.76.104.132]) by postgresql.org (Postfix) with ESMTP id 8B71A9FA2C6 for ; Wed, 1 Aug 2007 15:17:29 -0300 (ADT) Received: from dilbert (host-208-65-241-192.static.295.ca [208.65.241.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smaug.vex.net (Postfix) with ESMTP id 97FB91797C; Wed, 1 Aug 2007 14:17:27 -0400 (EDT) Date: Wed, 1 Aug 2007 14:17:24 -0400 From: "D'Arcy J.M. Cain" To: "Scott Marlowe" Cc: "John Mitchell" , pgsql-sql@postgresql.org Subject: Re: How do I connect postgres table structures and view structures to an existing svn repository? Message-Id: <20070801141724.49097d23.darcy@druid.net> In-Reply-To: References: <20070801113812.6a2d6fac.darcy@druid.net> X-Mailer: Sylpheed 2.4.3 (GTK+ 2.10.13; i386--netbsdelf) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL=0.002, BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200708/6 X-Sequence-Number: 28944 On Wed, 1 Aug 2007 11:46:11 -0500 "Scott Marlowe" wrote: > On 8/1/07, John Mitchell 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. > > 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. You are right. It is always difficult to add structured control to unstructured development methods. The method that I suggested was the best I could think of to handle a database that is changed ad hoc with no design work beforehand. If you work from the design side first you can create schema documents that feed your database creation and use svn to save those versions and document exactly why things changed. -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.