Fernando, When you say...
"When you have too many migration files, simply remove them." ...I think this means that you refer to the schema as the one source of summary information and that migration files are not informative except when a developer wants to revert to an earlier stage via 'redo' or 'version'. Grar On Mar 19, 7:38 pm, Fernando Perez <[email protected]> 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
