Rails: Migration Errors

Question

when I go to my http://localhost:3000/ I am getting the following:

ActiveRecord::PendingMigrationError

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

Extracted source:

# Raises <tt>ActiveRecord::PendingMigrationError</tt> error if any migrations are pending.
def check_pending!(connection = Base.connection)
  raise ActiveRecord::PendingMigrationError if ActiveRecord::Migrator.needs_migration?(connection)
end
def load_schema_if_pending!

Also, when I tried to to the heroku run rake db:migrate in the console, it said:

StandardError: An error has occurred, this and all later migrations canceled: PG::DuplicateColumn: ERROR: column "email" of relation "users" already exists

I am new to ruby and followed the devise tutorial by Mackenzie Child. It's my last step to complete my first ruby application.

I am excited and looking forward to your help! :)

Gurmukh Singh · Accepted Answer · 2016-07-15 14:46:19Z

1

In your console run rake db:migrate Make sure you in the project directory

answered Jul 15, 2016 at 14:46

Gurmukh Singh

2,0474 gold badges32 silver badges73 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Leonel Galán Over a year ago

I might add, running heroku run rake db:migrate runs the migration on Heroku, not in your localhost. Errors like "PG::DuplicateColumn: ERROR: column "email" of relation "users" already exists" usually come from modifying the migrations name or version.

Matthias Cordes Over a year ago

Unfortunately it didn't help. When I do that I get: "rake aborted! StandardError: An error has occurred, this and all later migrations canceled:" Ater that: "SQLite3::SQLException: duplicate column name: email: ALTER TABLE "users" ADD "email" varchar DEFAULT '' NOT NULL" And then a lot of hundrets of lines about SQLite3 and activerecord

Nic Nilov · Accepted Answer · 2016-07-16 11:17:59Z

0

You used devise generator to prepare migration for your User model. Your model was already in place before and already had an email column. Devise-generated migration tries to create the same column and, expectedly, fails, that's the reason for the error you're seeing:

PG::DuplicateColumn: ERROR: column "email" of relation "users" already exists

To fix that just open your devise-generated migration and remove the line which looks something like this:

t.string :email...

Then run rake db:migrate.

UPDATE

Since your database seems to be out of sync with your migrations it might be advisable to recreate it from scratch.

Run

rake db:drop db:create db:migrate

Note that all database data will be destroyed.

edited Jul 16, 2016 at 11:17

answered Jul 15, 2016 at 15:59

Nic Nilov

5,1652 gold badges24 silver badges38 bronze badges

4 Comments

Matthias Cordes Over a year ago

I tried it and still get an error after rake db:migrate, which looks like this: rake aborted! StandardError: An error has occurred, this and all later migrations canceled: SQLite3::SQLException: duplicate column name: encrypted_password: ALTER TABLE "users" ADD "encrypted_password" varchar DEFAULT '' NOT NULL /Users/matthiascordes/.rvm/gems/ruby-2.3.1/gems/sqlite3-1.3.11/lib/sqlite3/database.rb:91:in initialize' /Users/matthiascordes/.rvm/gems/ruby-2.3.1/gems/sqlite3-1.3.11/lib/sqlite3/database.rb:91:in new' ...and so on

Matthias Cordes Over a year ago

and also this instead: SQLite3::SQLException: no such table: users: ALTER TABLE "users" ADD "encrypted_password" varchar DEFAULT '' NOT NULL

Matthias Cordes Over a year ago

I pushed everything up to github (commits). Is there an easy way to restore everything from there?

Nic Nilov Over a year ago

Make sure this works locally first and when it does just push a new commit with the correct code state.

Collectives™ on Stack Overflow

Rails: Migration Errors

2 Answers 2

2 Comments

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related