One method I have used is "database migrations" included in Ruby on Rails. Essentially each version of your database includes up and down changes. Up changes are the changes needed to bring the database from previous version, and Down changes are the reverse.
You may be able to create a lot of code to automate a lot of this functionality, but you can also do it manually. The benefits mean you can check in these migrations into your normal VCS so they get version controlled as well. The RoR docs may give you some ideas on how to code it yourself. http://guides.rubyonrails.org/migrations.html On Fri, Jul 12, 2013 at 8:37 AM, Chris London <[email protected]> wrote: > I just wanted to see what everyone is using to try and manage database > deployment/version control for the following use cases: > > 1) Database schema changes. Being able to roll out and roll back database > schema changes from development to staging to live. > > 2) Database data changes. Being able to roll out and roll back inserts, > updates, and deletes to databases. (this one poses a unique problem which > auto increment ids) > > Thanks everyone, > Chris > > _______________________________________________ > > UPHPU mailing list > [email protected] > http://uphpu.org/mailman/listinfo/uphpu > IRC: #uphpu on irc.freenode.net _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
