On 12 July 2012 18:38, Andy Chambers <achambers.h...@gmail.com> wrote: > On Thursday, July 12, 2012 12:37:33 PM UTC-4, Walter Lee Davis wrote: >> >> >> On Jul 12, 2012, at 12:30 PM, Jean-Sébastien D. wrote: >> >> > Walter Davis wrote in post #1068458: >> >> On Jul 12, 2012, at 11:18 AM, Jean-Sbastien D. wrote: >> >> >> >>> rake db:rollback YYYYMMDDHHMMSS_model.rb >> >> I don't know specifically -- what do the guides say? I've only ever >> >> stepped back one or two at a time, made my adjustments, then run rake >> >> db:migrate again to roll back up to the current stage. >> >> >> >> Walter >> > >> > Thanks I appreciate, i find it weird that you must make a new migration >> > everytime you made a mistake, its seem to be a lot of overhead in >> > compilation time. Maybe something that future rails should invest. Who >> > knows I just started learning ruby. >> > >> >> The migrations are typically only run during development, and then you can >> install from the schema (which maintains a "current state" of the database >> at all times) > > > This is not true. Lets say you have a working system, being used by > thousands of users. The database has enough data that a backup/restore > takes half a day. Then you need to add a new feature that requires 3 new > tables, and new columns on an existing table. How are you supposed to do > this *without* running a migration against the production system?
I suspect Walter meant "during the development phase" rather than "in development mode". Migrations are applied to the production database during development. Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en-US.
