I can think of several ways to build this. I haven't seen anything like an off-the-shelf automated product though.
To me, automagically rolling back schema changes seems fraught with potential for disaster? You may not be able to get lost data back unless you take a backup of your db just before rolling back the schema changes.
On Wed, Sep 16, 2009 at 4:14 PM, Alan Puccinelli
<[address removed]> wrote:
Has anyone come across a good method for keeping their source code and database schema in sychronized version control so that you can roll back code and schema simultaneously if need be?
In particular I would be super stoked if there were something out there like springloops (www.springloops.com- web based SVN manager) with a web GUI that keeps your DBs in sync and allows you to easily deploy from dev to production.
Is this just wishful thinking or has anyone seen it?
-Alan
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Alan Puccinelli ([address removed]) from The San Francisco PHP Meetup Group.
To learn more about Alan Puccinelli, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA