> Matt, your conversation with DHH sounds like it touched on migrations > versus schema dumper. I'd love your thoughts (or David's!) on the > subject of migrations for building the test DB.
Migrations were never meant to be data seeders. They were meant to change the schema and massaging existing data to fit the new schema. In that context, it doesn't make sense to use migrations for the test database because the test database does not have permanent data of importance. But it seems that this misuse of migrations highlights something that might be lacking: a data seeding system. People are cajoling migrations to fit that role too even though it wasn't designed as such. So we should think about addressing that concern as a separate function. For me personally, fixtures fulfill the seeder role for the test database. I'm interested in knowing when that doesn't work for others. BTW, I agree that fixtures should not be used to seed the production database. That's another concern that Rails doesn't really address at the moment. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
