subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Albertson <albertson.ch...@gmail.com>
Subject Re: MySQL changes into svn
Date Mon, 28 Feb 2011 20:35:26 GMT
>>> Whenever I change my MySQL database, I do then manually run a script that
>>> saves the schema to a file, then I commit that file to my Subversion
>>> repository. I try to limit myself to one database change at a time, so
>>> that I can write reasonable commit messages.
>>
>> I am wondering the same thing, how to automate database backup. There is a
>> tool in Linux for automatic database backup, but it seems quite buggy. I have
>> been able to backup my databases using a bash script and a pre commit hook
>> could be the next thing to do, but still no automation there.
>
> Subversion is not a backup system.
>

Perfectly OK the place a __schema__ in SVN.  But it is not reasonable
to use SVN to store the content of a database.

Most every SQL database I've seen has a "dump" command that will dump
content to an ASCII file.  Then you save the files the same way you'd
save any other files.  You __do__ have to do the dumps inside a
transaction so to maintain consistency.


-- 
=====
Chris Albertson
Redondo Beach, California

Mime
View raw message