You can try to do a 'rake db:drop' to drop all tables, then do a 'rake db:create' and then finally again do 'rake db:migrate' Regarding the error in your second rake file, can you please share the migration code within that file ?
Thanks & Regards, Dhruva Sagar. Pablo Picasso<http://www.brainyquote.com/quotes/authors/p/pablo_picasso.html> - "Computers are useless. They can only give you answers." On Mon, Aug 31, 2009 at 9:43 PM, zambezi <[email protected]> wrote: > > I've encountered a problem running Rake migrations. This is in a > fresh database (no prior migrations run). > > 001_create_incident_users > 002_create_incidents > > Running db:migration resulted in table incident_users being > successfully created, but Rake then aborted before migrating/creating > the second table. > > So I then tried the following three permutations to coax a successful > migration of the incident table and got the same result each time. > Basically an incident_user migration is run (rather than incident) and > then the process aborts. The log file didn't have anything further to > offer. > > db:migration > db:migration incidents > db:migration VERSION=002 > > (in C:/RubyRails/rails_apps/rappEAHv8) > == 2 CreateIncidentUsers: migrating > =============================================== > -- create_table(:incident_users) > rake aborted! > Mysql::Error: Table 'incident_users' already exists: > > So I thought I would see if anyone has more of a clue than I do before > falling back on the MYSQL command line editor just to get things > moving along. > > Thanks much, > Bill > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
