Matt mentioned something along the lines of db:cycle, which, I believe would:
desc 'Drops and recreates the database from migrations for the current environment.' task :cycle => ['db:drop', 'db:create', 'db:migrate'] Ryan On Dec 9, 2007, at 10:47 AM, eggie5 wrote: > > Considering the fact that a lot of people add simple bootstrapping > routines in their migrations, it seems to make sense to me for > db:reset to NOT run off migrations and to use the same name for the > task that uses migrations to db:reset WITH=migrations (schema would be > default) or db:reset_with_migrations. > > Since the 2 task (reset by schema or migraitons) provide similar > functionality, just by different means, it makes sense to have that > association by name. So as you can see I don't agree with the new name > 'migrations:reset'. > > No input on db:redo. > > Additionally, I think it would be handy to have a task that, based a > list of tables as arguments, drops the table and creates it again > based on it's migration file. Would anybody else find this handy? > > Alex Egg > > On Dec 9, 2:05 am, "Matt Aimonetti" <[EMAIL PROTECTED]> wrote: >> I have now 3 objectives as Ruby developer. >> >> 1. get as many people as I can to recommend me on working with >> rails >> (http://www.workingwithrails.com/recommendation/new/person/6065-matt-a... >> ) >> ( Linkedin would work too) (Patrick, I hope you're proud of me) >> >> 2. find a solution to the recent change in rake db:reset. (this >> objective is >> actually serious) >> >> As some of you know, a while ago, I contributed few rake tasks to >> Rails 2.0. >> Rake db:reset being of the task I was using the most, I got really >> annoyed >> when DHH changed its behavior to load the schema.rb file instead of >> using my >> good old migrations. We exchanged few emails and he explained his >> view >> point. While he had a good point, I was still really annoyed at the >> fact >> that I had to add my custom tasks to do what I used to have builtin. >> >> Finally tonight, that was it, I couldn't handle it anymore and I >> submitted 2 >> new patches: >> >> http://dev.rubyonrails.org/ticket/10431http://dev.rubyonrails.org/ticket/10432 >> >> public >> discussion:http://groups.google.com/group/rubyonrails-core/browse_thread/thread/ >> >> ... >> >> Please feel free to react to my suggestion, suggest better names or >> solutions, but let's get this problem fixed ASAP. >> >> 3. I forgot my last objective, make San Diego the Ruby capital! We >> are >> ranked #5 at the >> momenthttp://www.workingwithrails.com/browse/groups/authority >> (if you didn't >> signup for a WWR account, it's time ! don't forget to join our >> group and >> recommend us ;) ) >> >> -- >> --------http://railsontherun.com > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
