On Apr 1, 1:48 pm, Max Williams <[email protected]> wrote: > > Ways around it i can think of ... > > a) i make sure that my migrations don't use something from the codebase > which is going to be deleted in the future. This seems difficult if not > (conceptually at least) impossible. When you're doing a refactor you > often have to use the old system/data to configure the new data. >
Create private copies of the classes involved in the migration ie class ChangeQuizzes < ActiveRecord::Migration class Quiz < ActiveRecord::Base; end ... end obviously include only what behaviour the migration actually needs. Fred -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
