On Tue, Sep 8, 2009 at 2:01 PM, Michael Koziarski <[email protected]> wrote: > That'd work only for cases where your down migrations *only* change > the schema, they don't touch models or any other ruby code. Otherwise > there's no guarantee that those models are available when the system > tries to downgrade.
Doesn't this same problem exist always - whether you are going down or up, or store your migrations in files or the database? Some would consider it an antipattern to put any models or app classes in your migrations. I'm still not clear on the original poster's root problem and solution, but I don't think the possibility of outdated non-schema migration code is a good reason to reject the idea. -- Chad --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
