On Apr 10, 1:53 pm, Steven Soroka <[email protected]> wrote: > I think the primary reason developers do this is because there isn't a > good alternative.
I think there are a number of reasonably good techniques available. The top two results for this Google search are probably a good starting point: http://www.google.com/search?q=rails+seed+data Personally, I'm happy just creating my own "rake db:populate" task and invoking that when necessary. Still, I think there's room for some convention to emerge here. I just don't we're at the "one really popular plugin or technique emerges as the winner" part. Maybe a good way to approach the problem would be to create a plugin or technique and to try and promote it as the best solution. Perhaps then, if appropriate, someone on Rails Core would see fit to pull it into Rails proper. If not, you could at least have a popular plugin on your hands :) - Trevor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
