[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Managing SQL in the repository

From: Mark <mark_at_msdhub.com>
Date: 2004-06-01 18:24:28 CEST

We recently started managing our database schema in svn, and we came up with
a similar method, with one difference. When a dev checks in a change to a
create (table|proc|func|...) script, they must also check in an alter or a
drop/create than will migrate the current version to the new version,
enforced by a pre-commit hook. That way, for any given revision, the raw
creates and the last tag's creates + subsequent modifications will give the
same schema.

This might only be possible because we're a pretty small team (6) of people


-----Original Message-----
From: Gary Affonso [mailto:glists@greywether.com]
Sent: Monday, May 31, 2004 1:05 PM
Subject: Re: Managing SQL in the repository

On 5/30/04 4:08 PM, "m christensen" <dfs@xmission.com> wrote:

> I don't know what you mean by "keeping configuration data in the DB".

You original reply stated this:

> #3 Compiled binaries often pull parameters or configuration info from
> the database

This item doesn't apply to our situation.

- Gary

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 1 18:26:02 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.