> > IMO, I'd love to see a seed system that mimics migrations a bit and > keeps the standard AR syntax that we are used to: Person.create(...). > > If we have a version-based data-seeding system then we've really just created a parallel set of migrations. Same benefits, same problems. Once the models are out of date (say you move a field from one table to another) then your older seed files will be broken. Yet, if we don't use a version-based system then it's difficult to know what actions to perform to update a given environment. Adding missing data is easy enough but how do you track when data was removed?
I can see now why we haven't had any kind of data-seeding mechanism and why many of us (myself included) cannibalized migrations for that purpose. ::Jack Danger --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
