A database in Subversion?


This is interesting, but why in gods name would you do this?


I just don’t see the need for storing databases in version control. I do think that databases should be version controlled, but not the data itself. Dump the DDL and version control that. Does the data really need to be there? I supposed I can think of some arguments to do it, but it sure rubs me the wrong way. I’m guessing that 99% of the time this is NOT what I would suggest doing.

powered by performancing firefox

1 thought on “A database in Subversion?”

  1. I agree, it’s not something you’d want to do very often. In this case, we have a distributed team working on a database project without a shared server. The database is pretty small and is used to drive reports. This is a simple way to share the database between developers and have a backup in case a new version of the database causes a problem. It would be a good amount of work to dump the DDL and script all the data (which is important for the reports). The file’s 350K when zipped; which is pretty small in the big scheme of things.

Comments are closed.