CODEWITHSUNDEEP
ruby-on-railspostgresql
Leag Er
Leag Er

Reputation: 261

PG::DuplicateTable: ERROR: relation "posts" already exists

When I run rake db:migrate I get following output:

== 20141219011612 CreatePost: migrating ======================================= -- create_table("posts") rake aborted! StandardError: An error has occurred, this and all later migrations canceled: == 20141219011612 Postposts: migrating ======================================= -- create_table("posts") rake aborted! StandardError: An error has occurred, this and all later migrations canceled:

PG::DuplicateTable: ERROR: relation "posts" already exists : CREATE TABLE "posts" ("id" serial primary key, "post" text, "release_date" timestamp, "created_at" timestamp, "updated_at" timestamp) /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql/database_statements.rb:128:in async_exec' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql/database_statements.rb:128:in block in execute' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract_adapter.rb:373:in block in log' /home/admin/.rvm/gems/ruby-2.1.5/gems/activesupport-4.1.8/lib/active_support/notifications/instrumenter.rb:20:in instrument' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract_adapter.rb:367:in log' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql/database_statements.rb:127:in execute' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/schema_statements.rb:205:in create_table' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/migration.rb:649:in block in method_missing' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/migration.rb:621:in block in say_with_time' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/migration.rb:621:in say_with_time' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/migration.rb:641:in `method_missing'

...

migrate' /home/admin/.rvm/gems/ruby-2.1.5/gems/activerecord-4.1.8/lib/active_record/railties/databases.rake:34:in block (2 levels) in <top (required)>' Tasks: TOP => db:migrate (See full trace by running task with --trace)

I don't understund how this is possible, bescause In scheme file I don't have post table.

Upvotes: 26

Views: 46187

Answers (8)

stevec
stevec

Reputation: 52238

I had the same problem, the only thing that worked for me was to delete the table from within the rails console, like so:

ActiveRecord::Migration.drop_table(:products)

Upvotes: 1

Nuha
Nuha

Reputation: 324

This will delete your data, don't do it on production. First remove the orphan migration ********** NO FILE ********** in case you have any, by executing this db command:

delete from schema_migrations where version='<MIGRATION_ID>';

then

rails db:schema:load

then

rails db:migrate

This worked for me.

Upvotes: 0

Shiva
Shiva

Reputation: 12514

For those who didn't get your answer above

In my case, I had been working on a feature a month ago the field happens to be created at that time. Now when I try to run migration rake db: migrate I see this error. I know and am sure that this is not here due to any mistake.

I also tried to rollback that particular migration

rake db:migrate:down VERSION=20200526083835

but due to some reason, it did nothing, and to move further I had to comment out the up method in that migration file.

# frozen_string_literal: true

class AddColToAccounts < ActiveRecord::Migration
  def up
    # execute 'commit;'
    #
    # add_column :accounts, :col, :boolean,
    #            null: false,
    #            default: false
    

  end

  def down
    execute 'commit;'

    remove_column :accounts, :col
    
  end
end

And, now I am able to run the migrations.

At last, I undo the commenting thing and I am done.

Thanks

Upvotes: 4

Duarte
Duarte

Reputation: 11

kill the current postgres process:

sudo kill -9 `ps -u postgres -o pid`

start postgres again:

brew services start postgres

drop, create, and migrate table:

rails db:drop db:create db:migrate

Upvotes: 0

Sandip Subedi
Sandip Subedi

Reputation: 1077

One of the hack I found was to put pry before you are creating the table on the migration file.

require 'pry'
binding.pry

create_table :your_table_name

and drop that table:

drop_table :your_table_name

After that you can remove the drop_table line and it will work fine!

Upvotes: 0

Adam Grant
Adam Grant

Reputation: 13105

In case this helps anyone else, I realized that I had been using a schema.rb file that was generated while using MySQL. After transitioning to Postgres, I simply forgot I would need to run rake db:migrate before I could use rake db:schema:load

Upvotes: 0

shikha
shikha

Reputation: 669

Check your db/schema.rb

You most likely have the same table being created there in addition to a migration in db/migrate/[timestamp]your_migration

You can delete the db/migrate/[timestamp]your_migration if it is a duplicate of the one found in the schema and it should work.

Upvotes: 1

Bill Doughty
Bill Doughty

Reputation: 2310

Somehow, you ended up with a table named 'posts' in your database. Perhaps from a prior migration that you deleted without rolling back? If you don't care about any of your data in the database, you can run

rake db:drop db:create db:migrate

to bring your development database inline with your current migrations.

If you have data in other tables you don't want to lose, open the database console and drop the posts table manually:

$ rails db

# drop table posts;

Then run db:migrate again.

Upvotes: 88

Related Questions