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) when you get to production. Migrations are a great way to build an application organically, because you can roll them back and undo a spike you tried and didn't like. Use them like Git for your database. Walter > Thanks > > -- > Posted via http://www.ruby-forum.com/. > > -- > 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. > -- 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.
