Forum: Ruby on Rails Data Migrations in Production

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
B0f5d09953d14dcc7705f928d503c824?d=identicon&s=25 Mike Cahill (mike-in-dc)
on 2008-12-27 04:05
(Received via mailing list)
General question - when you deploy a new production version, how do
you normally handle the data migration?  I'm leery of applying "spot"
changes directly to the prod DB - I would prefer to have an unchanged
version to roll back to.  (Could always backup and restore of
course...)    I haven't seen much literature on running a data
migration script to move from one prod DB to another with changes
applied on the fly, so I'm guessing people don't do that...
81b61875e41eaa58887543635d556fca?d=identicon&s=25 Frederick Cheung (Guest)
on 2008-12-27 13:16
(Received via mailing list)
On 27 Dec 2008, at 03:04, Mike wrote:

>
> General question - when you deploy a new production version, how do
> you normally handle the data migration?  I'm leery of applying "spot"
> changes directly to the prod DB - I would prefer to have an unchanged
> version to roll back to.  (Could always backup and restore of
> course...)    I haven't seen much literature on running a data
> migration script to move from one prod DB to another with changes
> applied on the fly, so I'm guessing people don't do that...

As far as being able to roll back to stuff, we just stop replication
between the master and the primary slave while we do migrations etc...
If it all goes tits up we can fallback to the slave which has the
database prior to the migrations and also has the previous version of
any code that it runs.

Fred
This topic is locked and can not be replied to.