It seems to me that data migrations have a serious flaw when refactoring models and the database schema -- they are coupled to the model class relationships. If I''m trying to get *rid* of old relationships in favor of new changes to the schema, I eliminate the ability to back down through previous data migrations, or even to drop the database and migrate from scratch. Are there techniques for dealing with this? Should I be using something other than the model relationships in the data migration? Should I be checking respond_to? in the migration? (In which case I would be forced to abandon data.) -- Posted via http://www.ruby-forum.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 -~----------~----~----~----~------~----~------~--~---