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

Re: Version control of Databases

From: Daniel Patterson <danpat_at_danpat.net>
Date: 2005-06-14 07:46:59 CEST

Mark Parker wrote:
> We tried something like that. We discovered that mere mortal humans
> don't have the discipline to ensure that what the create-from-scratch
> script makes and what the upgrade-from-previous script mades aren't
> always the same. We ended up with a
> create-from-scratch-and-use-a-sync-tool approach that we're quite happy
> with.

  Have you looked at the approach that Bugzilla takes? Basically, there
  is one great big "create-database.sh" script which is *all* written
  as changes. Last time I looked, a new installation created a minimal
  schema, and then applied a whole stack of changes that have accumulated.

  Whenever someone wants to make a change to the schema, they add it to
  the bottom of the script, along with a test to see if that change
  has already been applied. Seems to work well enough. I believe someone
  generates a "current schema" for new installations with each release
  to, but those schemas are generated at compile time and are not
  under version control (they can be generated from the "create-database.sh"
  script, or whatever it's called).

  There is no ability to downgrade with this setup (yet), but I guess
  it could be added.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 14 07:49:46 2005

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.