[Rails] Re: Why is AR migrations using one file per migration?

On May 14, 8:58 pm, Nicolas Buduroi <nbudu...@gmail.com> wrote:
> Hi, I'm currently in the process of rethinking some of the design decisions
> I've taken in my first attempt to add migrations support to Lobos, a Clojure
> schema manipulation library. I've based this work mostly on ActiveRecord,
> but now that I'm getting some feedback on it, I really wonder why Rails
> migrations are spread around into individual files. Wouldn't it be better to
> simply add the timestamp to the migrations name and put them all into one
> file?
>
Just off the top of my head, it is probably easier to write a
generator that creates a new migration file than one that edits an
existing file

Fred

> Here's the discussion that made me ask this question:
>
> https://groups.google.com/d/topic/lobos-library/GnFBKahrhY0/discussion

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.