Keeping a database structure up to date in a project where code is on subversion?

Posted by Bruno De Barros on Stack Overflow See other posts from Stack Overflow or by Bruno De Barros
Published on 2010-04-03T12:44:20Z Indexed on 2010/04/03 12:53 UTC
Read the original article Hit count: 322

Filed under:
|

I have been working with Subversion for a while now, and it's been incredible for the management of my projects, and even to help managing the deployment to several different servers, but there is just the one thing that still annoys me. Whenever I make any changes to the database structure, I need to update every server manually, I have to keep track of any changes I made, and because some of my servers run branches of the project (modifications that are still being worked on, or were made for different purposes), it's a bit awkward.

Until now, I've been using a "database.sql" file, which is a dump of the database structure for a specific revision. But it just seems like such a bad way to manage this.

And I was wondering, how does everyone else manage their MySQL databases when they're working on a project and using Subversion?

© Stack Overflow or respective owner

Related posts about mysql

Related posts about subversion