Rails - Aug 2007 - Handling changes in models in migrations

Hello Rails list,

I had a question regarding dealing with changes to models and
migrations.  When a model has its name changed or is deleted in a
newer migration this has the possibility of breaking an earlier
migration that believes that model still exists but doesn''t.

How have been handling this?   The Rails wiki suggests to not use
application models in a migration or try to create temp models to
handle this case.  However, on a project our team has been working on
the number of migrations that would have to be touched to fix this is
quite unwieldy.

How have people here been trying to deal with this situation?  Don''t
get into it?   :-) Some magic ruby-fu to convert all bad migrations
into a good one?  Ignore it and deal with the problem when it happens?


Cheers,
Alain

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

On 8/14/07, Alain Hoang <hoanga-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
>
> Hello Rails list,
>
> I had a question regarding dealing with changes to models and
> migrations.  When a model has its name changed or is deleted in a
> newer migration this has the possibility of breaking an earlier
> migration that believes that model still exists but doesn''t.
>
> How have been handling this?   The Rails wiki suggests to not use
> application models in a migration or try to create temp models to
> handle this case.  However, on a project our team has been working on
> the number of migrations that would have to be touched to fix this is
> quite unwieldy.
You should be doing this from the start then.  Or, just remove the old
migrations.

-- 
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---