Starting with versioning mysql schemata without overkill. Good solutions?

Posted by tharkun on Stack Overflow See other posts from Stack Overflow or by tharkun
Published on 2009-04-16T11:28:44Z Indexed on 2010/03/25 9:03 UTC
Read the original article Hit count: 345

I've arrived at the point where I realise that I must start versioning my database schemata and changes. I consequently read the existing posts on SO about that topic but I'm not sure how to proceed.

I'm basically a one man company and not long ago I didn't even use version control for my code. I'm on a windows environment, using Aptana (IDE) and SVN (with Tortoise). I work on PHP/mysql projects.

What's a efficient and sufficient (no overkill) way to version my database schemata?

I do have a freelancer or two in some projects but I don't expect a lot of branching and merging going on. So basically I would like to keep track of concurrent schemata to my code revisions.

[edit] Momentary solution: for the moment I decided I will just make a schema dump plus one with the necessary initial data whenever I'm going to commit a tag (stable version). That seems to be just enough for me at the current stage.[/edit]

[edit2]plus I'm now also using a third file called increments.sql where I put all the changes with dates, etc. to make it easy to trace the change history in one file. from time to time I integrate the changes into the two other files and empty the increments.sql[/edit]

© Stack Overflow or respective owner

Related posts about php

Related posts about mysql