> 1 ) What, then, is the preferred mechanism for "seed" data in the > database? Currently, many people use migrations to insert bootstrap > data. If schema.rb will be used for tasks like db:reset, none of this > data will be loaded.
For a production database, migrations are the obvious option. I'll probably get lynched but I just load fixtures to get my laptop's data good to go... > 2 ) What about those of us who specify additional options like charset > or table types? This information, last time I checked, doesn't seem to > be saved in the schema.rb. Use the :sql schema format, perhaps you could supply patches to have the rake tasks figure out which importer to run based on that setting? > 3 ) Should there be yet another database-related Rake task for > development? Many of us create migrations, then modify them until > we're ready to commit. A simple "rake db:reset" used to re-run the > migrations from scratch, but the new semantics mean that migration > changes are never reflected. rake db:drop db:create db:migrate will do what you need. if you think there should be a task for this, come up with a name and a patch and we can take a look. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
