It's the same basic strategy I've been using successfully for the past 15+yrs dev'ing and maintaining web apps, using various mvc frameworks, langs, etc. Don't follow it if you don't want, but it's one that's worked well for me, based on real-world experience, and saved me a lot of time/headaches.
Jeff On Mar 19, 4:38 pm, Fernando Perez <li...@ruby-forum.com> wrote: > > I prefer to keep one migration per model > > It's a bad an unmaintainable idea. I did that when I was a beginner in > RoR. > > Simply create migrations to add/remove columns to existing tables. When > you have too many migration files, simply remove them. The whole schema > is saved in schema.rb > -- > Posted viahttp://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-t...@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.
