On Wed, Sep 9, 2009 at 4:02 PM, Rick DeNatale <[email protected]> wrote: > My normal practice when writing migrations which depend on model code > is to put a migration specific model clase in the migration file > itself, scoped inside the migration. The model mimics a subset of the > one in app/models including only necessary attribute declarations and > methods.
Great idea, thanks... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
