rails: `rails db:drop:all db:create:all db:migrate` isn't creating tables after adding InternalMetadata/EnvironmentMismatchError

I found a solution for myself. Here we go:

I was encountering ActiveRecord::NoEnvironmentInSchemaError with pg and started inspecting my databases.

The key difference I found was my ar_internal_metadata had the column key set as integer on DBs having issues and DBs not having issues key was set to varchar and had a value of environment

Also my schema which was loading was doing this:

create_table "ar_internal_metadata", primary_key: "key", force: :cascade do |t|
  t.string   "value"
  t.datetime "created_at", null: false
  t.datetime "updated_at", null: false
end

The schema should be like:

create_table "ar_internal_metadata", primary_key: "key", id: :string, force: :cascade do |t|
  t.string   "value"
  t.datetime "created_at", null: false
  t.datetime "updated_at", null: false
end

Now everything works. Hope this helps others. I’m guessing it got screwed up some how in the rails4 to rail5 migration.

app:update task (that should be run after upgrade, according to the guide) deals with it. AFAIU it is intended behavior.

@andrewyoo that schema difference was the cause of my issue as well. I deleted that table manually and re-ran rails db:migrate and it resolved itself. Sounds like this issue might need to re-open?

@Schwad I came here by googling. My problem may not be the same but seems related. And I have a super-simple reproduction:

git clone git@github.com:publify/publify_amazon_sidebar.git
cd publify_amazon_sidebar
bundle exec rake

I get the following output:

/home/matijs/.rbenv/versions/2.3.1/bin/ruby -I/home/matijs/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib:/home/matijs/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rspec-support-3.5.0/lib /home/matijs/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
rails aborted!
ActiveRecord::EnvironmentMismatchError: You are attempting to modify a database that was last run in `development` environment.
You are running in `test` environment. If you are sure you want to continue, first set the environment using:

	bin/rails db:environment:set RAILS_ENV=test

bin/rails:4:in `require'
bin/rails:4:in `<main>'
Tasks: TOP => db:test:load => db:test:purge => db:check_protected_environments
(See full trace by running task with --trace)
Run options: include {:focus=>true}

All examples were filtered out; ignoring {:focus=>true}

[snip rest of successful RSpec run output]

You’ll get that error if you’re trying to run that command on a non-empty database that was upgraded from Rails 4.2. To resolve it follow directions, run that command. That error is expected, there’s no way around it, running it is part of the upgrade process.

I’m running off of a rails new app with Rails 5 pointing at master in the Gemfile.

This command also works:

$ rails db:drop db:create db:migrate --trace

I’m thinking there’s some strange interaction with the :all invocations.

It will be helpful if someone will write how you’ve got wrong column type in schema.

I strangely got this error when checking out a pre Rails 5 commit in our repo, loading schema from that commit and then going back to HEAD commit with Rails 5.

Ryans-MacBook-Pro:matic-home ryanquant$ bin/rails db:reset
I, [2016-11-28T08:55:41.209693 #15269]  INFO -- : Celluloid 0.17.3 is running in BACKPORTED mode. [ http://git.io/vJf3J ]
rails aborted!
ActiveRecord::NoEnvironmentInSchemaError: 

Environment data not found in the schema. To resolve this issue, run: 

        bin/rails db:environment:set RAILS_ENV=development

Any db rake/rails command I tried to run would cause the error to be thrown (even after running the environment setup command recommended in the error).

Strangely, when the one exception is when I ran bin/rails db:migrate. The normal behavior resumed and the errors were no more.