Rails migration does not change schema.rb

Question

I have a rails migration that is not being applied to my schema.rb. The migration should create a table:

class CreateUserGraphs < ActiveRecord::Migration
  def change
    create_table :user_graphs do |t|
      t.string :name
      t.string :content
      t.integer :user_id
      t.string :type_id
      t.integer :upload_id

      t.timestamps
    end

    add_index :user_graphs, [:user_id, :created_at]
  end
end

I did db:reset. Then I tried rake db:migrate:up VERSION=123123123(this is the migration #). I am in my "dev" environment.

Why is the migration not affecting schema.rb?

Did you try to drop the database first? rake db:drop db:create db:migrate — Vucko
Interesting that worked. How does rake db:drop db:create differ from rake db:reset? — Don P
rake db:reset runs db:create db:schema:load db:seed without the migrations. I think that db:migrate:reset will suit your needs. — Vucko
@Vucko, please add this suggestion as a valid answer to the question ;) — marzapower

Vucko Vucko · Accepted Answer · 2013-12-09T09:00:57

From the documentation:

The rake db:reset task will drop the database, recreate it and load the current schema into it.

This is not the same as running all the migrations. It will only use the contents of the current schema.rb file. If a migration can't be rolled back, 'rake db:reset' may not help you. To find out more about dumping the schema see 'schema dumping and you.'

So rake db:reset => db:drop db:create db:schema:load db:seed

To run all the migrations, use : rake db:drop db:create db:migrate

Or db:migrate:reset=> rake db:drop db:create db:migrate

Reference

Rails migration does not change schema.rb

6 Answers