Hello,
I have been digging for weeks, and I just can't find a solution that works for me. Prior to now I've been making full db dumps from phpmyadmin and throwing them with my commits in SVN. I now have another person working on the project with me, and I'm not sure how well doing full db dumps is going to work between 2 people trying to work on the project at the same time. I get the feeling there's a huge potential for conflicts to occur, and it's not going to be very helpful to have to sift through database conflicts anytime one of us wants to commit.
In short, what's the best solution to get an SVN-friendly database dump?
I have looked into the Autopilot module, the Migraine & Sympal scripts, however they all seem to tackle the issue of managing staging & production servers- definitely worth considering when we're ready, but the site won't be public for several more months. For now, we just need a safe way to handle keeping the db in version control.
Any help that can be offered would be greatly appreciated. I have been searching relentlessly for a solution and I'm coming up short.
Comments
I figured it out thanks to
I figured it out thanks to the developers of the Autopilot module. We're now tracking all configuration changes with the Macro module, part of the Devel module package. Hope that helps anyone that stumbles on the same problems.
Just move database to your project folder
All you need is move database to your project folder, to do it you may read http://dev.mysql.com/doc/refman/5.0/en/windows-symbolic-links.html