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

Re: database version control

From: Tony Morris <tmorris_at_tmorris.net>
Date: 2007-01-31 04:33:30 CET

You won't be able to, since you have lost transaction management. You
have a few workarounds though:
1) You could run a cron job that constantly does a mysqldump and commits
to a svn repository
2) You could use a pure functional programming language that uses monads
for expressing database 'updates' and write your own little (ala
Haskell) application. Some of these already exist in Haskell

http://haskell.org/

Tony Morris
http://tmorris.net/

Ken Perl wrote:
> I'm not very clear with your aproach. I want to use subversion to
> control MySQL database table structure and data in all tables, when
> something's wrong, I can roll back and know who changes what.
>
> On 1/30/07, Eric Lemes <ericlemes@gmail.com> wrote:
>> On 1/30/07, Ken Perl <kenperl@gmail.com> wrote:
>> > hi,
>> >
>> > is it possible to do database version control using subversion?
>> >
>> >
>> I like to keep versioned the database model file (like the .er1 file
>> our the
>> .dm1 file) and/or the scripts that generates a new/fresh database
>> (including
>> the initial data necessary to run the application).
>>
>> This requires to create a new culture to some developers to change
>> *first*
>> the source control (.dm1 and scripts) and after that apply in the
>> database.
>>
>> Any other approach?
>>
>>
>> Eric
>>
>
>

Received on Wed Jan 31 04:33:57 2007

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