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

Re: versioning a [small] MySQL database with svn?

From: Ed MacDonald <edmacdonald_at_hotmail.com>
Date: 2005-02-27 20:06:10 CET

----- Original Message -----
From: "Basile STARYNKEVITCH" <basile@starynkevitch.net>
Subject: Re: versioning a [small] MySQL database with svn?

> So I will wrap svn commit inside a shell script, but I still believe
> it is a pity that *transforming* commands (like mysqldump) cannot be
> invoked at commit time by the svn commit command.
> I still believe that modern version control systems should be able to
> version-control user data which is not in plain textual (or platform
> neutral binary) form, of which a database is a typical example (and I
> listed others). And I don't want to version-control a huge database,
> only a small one. (people think of databases as always being gigabytes
> or terabytes, but it does make sense to use MySQL on a database of a
> few megabytes at most, and to want to version-control it).

While I may not fully agree with the use-case as presented, I think the idea
of client-side hooks for *transforming* would be very useful. For instance
my diff tool accepts plug-ins for pre-processing different files types prior
to a compare. One example of where it would be useful in SVN is for
applying code formatting tools (jalopy, tidy, etc) prior to check in. I
know it's not that difficult for a developer to do this sort of thing on
their own before committing. But the idea here is to help automate and
simplify a work-flow - just like the server-side scripts.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 27 20:12:47 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.