[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: Frank Gruman <fgatwork_at_verizon.net>
Date: 2005-06-09 19:49:35 CEST


I solve this by keeping all of the database creation/manipulation
scripts in version control as well. So as branches/tags are made, the
scripts are copied from one to the next. So when a do a release build,
I can also include the proper DB changes.

Hope that helps.


Gabor Szabo wrote:

>When developing an application that uses database an interesting
>question arises on how to track the changes you made to the database.
>Changes can be in schema (including indexes, user rights),
>in meta data (e.g. you might keep the string translations of your
>application in an database),
>some might even require some changes to the application data.
>(e.g. in an application earlier the user table had an e-mail field but
>in the new version you
>enable unlimited number of e-mails so you moved the e-mail column of
>the users table
>to a separate table)
>Maybe a slightly better explanation of the problem can be see here:
>How do people maintain versions of a database ?
>How do you make it easy to upgrade your application (including the database) ?
>I guess there might be applications providing some help with this.
>What integration exisits with Subversion ?
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 9 19:51:50 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.