Re: Combine old migrations?

On Sun, May 18, 2008 at 9:59 PM, Ryan Bigg (Radar)
<radarlistener@...> wrote:
> And before you say it,
>
> yes I could create a new migration and call drop_table in it, but then that
> defeats the purpose of only having one migration file.

Having only one migration file (per table?) gives the impression that
you are creating one migration file for each table, and when you want
to change the schema, you change the migration and go back and rerun
all the migrations?

If so this seems antithetical to the reason for migrations which is to
keep the history of changes to the DB schema as a series of deltas.

--

-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.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-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
-~----------~----~----~----~------~----~------~--~---