Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby Build a Todo List Application with Rails 4 Build a Todo List Application with Rails 4 Generate a Scaffold

Ruby Rails: Migrations are pending. To resolve this issue, run: bin/rake db:migrate RAILS_ENV=development

I keep getting this error, then i run the command through the prompt,

Migrations are pending. To resolve this issue, run: bin/rake db:migrate RAILS_ENV=development

5 Answers

Austin Davis
Austin Davis
23,939 Points

Did you already solve the problem? Did "bundle exec rake db:migrate" help or what did the trick?

Austin Davis
Austin Davis
23,939 Points

What command are you running through the prompt? Have you tried "bundle exec rake db:migrate"? What is it you are trying to do or have done so far?

no it didn't help, I tried that command again. I find that I spend more time trying to get things working in rails than actually programming

Austin Davis
Austin Davis
23,939 Points

Keep at it- that's where the learning happens. Try this "You need to do bundle exec rake test:prepare or bundle exec rake db:test:prepare and then bundle exec rake db:migrate before running the specs". It's from an answer on stack overflow to this same problem. If it doesn't work check it out at http://stackoverflow.com/questions/20082002/migrations-are-pending-run-bin-rake-dbmigrate-rails-env-development-to-resol?rq=1 .... follow links on the right hand side to similar questions and you are bound to find the answer or figure it out simply by considering the variety of answers.

I've actually looked at that exact stackexchange post last night before posting to these forums. I think I am going to restart the app from scratch and see if I run into the same problems.