Re: Combine old migrations?

> OK, so you wanted a "Why?", here's one.
>
> I create many migration files, lets say 20, with matching models in them is
> one called "Person". All of a sudden, I realise I don't like having it
> called Person and I never liked the idea of having a persons table. If I had
> combined my twenty migrations into one big migrations file I am now going to
> have to go looking through this HUGE file for my persons table, delete the
> entry, and then continue on my merry way. If I had a single file I could
> delete that file easily because I know what to expect when looking for it
> and I know exactly where it's going to be and I don't have to dig through a
> hundred lines looking for it.

Good, Ryan.  But you miss my point.  You have a tendency to present
your opinion/preference as fact.  My suggestion is instead to defer to
the wisdom of the developer in his or her own context.  As you post
your recommendation, assume that the developer has the ability to
discern whether or not your approach fits their context.  You do that
by giving the pro/con of your approach.

BTW, there is only one 'c' in Recommend.  You might want to change
that in your sig if you hope to attract would-be employers.  Folks
(like me) who are looking for Rails help see typos like that as an
indicator of the level of attention you pay to details, especially
when 'Recommend' can be copied and pasted from the WWR site.

Good luck.
--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---