On 20 August 2010 11:15, Zack Nathan <[email protected]> wrote: > Colin Law wrote: >> [..] >> In that case there must be something else wrong. Post the migration >> file (and it's name) and the full output from the migrate. Also the >> file db/schema.rb and we will see if we can work out what is >> happening. >> >> Colin > > Thanks, but I found the problem late last night. Simply the migrations > said that the migrate had happened , but it hadnt. So I just manually > updated the database.
In that case you have not found the problem, merely avoided it. In order to avoid it happening again I suggest that you roll back that migration using rake db:rollback (check the db to make sure it has rolled back) and then run it again and find out why it is not working. Otherwise you may find yourself in more of a mess when you attempt to run the next migration. Colin -- 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.
