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

On 15 May 2011 18:22, Nicolas Buduroi <nbuduroi@gmail.com> wrote:
> Yeah, while thinking about this, I realized how tiring it can be to
> search/consult/erase migrations files and I'm more and more sold to put all
> migrations into one file.

Why go half-way? Put all the models in one file too, bundle all the
controllers in with them, and you can whip the helpers in at the
bottom (we don't need them often)

Alternatively, there's no serious issue at all with having migrations
in separate files - yes, in one file I *can* merge them in my source
control software, but if they're in their own files I don't have to
bother. For the zero benefit that one migration file over lots of
files gives me, I can avoid the extra niggle of having to resolve
merge conflicts in it.

:-/

PS What do you ever search migrations for? Everything I've ever needed
is in schema.rb, or I just look in the DB...

--
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.