> My problem is not that my dev database is out of sync, in fact I thought the > use of migrations prevents this. My problem is that after a certain number > of migrations I can't migrate from zero on a new dev instance or new prod > server because my model is now in sync with migration 100, and something > fails at migration 8. This usually happens when adding or changing data in > the #8 migration. What would interest me more is some way to run a migration > using the same svn version for the model that that migration's last change > has. This isn't painful enough to me to actually write that code though. ;) >
I'd guess that the solution to this is purely a plugin material. But my preferred way is to include model definition inside migration for cases like that. -- Cheers! - Pratik http://m.onkey.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
