Rails db:migrate / db:create. Existed databases conflict

Question

I previously was making some webapps using Spring MVC + PostgreSQL on my PC.

Wanted to try RoR, faced strange prob with DB connection, google isn't helping.

I created i new Rails web-application, made one model and tried to make a migration. (Last Rails gem, 5.0.0.beta3)

The problem is:

When i'm running db:migrate/create/drop Rails is trying to manipulate my existing DB's instead of creation new ones.

-i have a few PostgreSQL databases on my local PostgreSQL server, which i still want to keep active on it. Lets say 'XXXXXXX', 'YYYYYYYYY', 'ZZZZZZZZZ'

Once i run db:create i get the following log:

C:\Users\****\RubymineProjects\sample_articles>rails db:create
'XXXXXXX' already exists

DB migrate is executed successfully and also creating one additional database 'sample_articles_development', which is the name as i specify in my database.yml. BUT the new tables appears to my existed database 'XXXXXXX'(which i didn't configure in any configs).

This is my database.yml config:

default: &default
  adapter: postgresql
  encoding: unicode
  # For details on connection pooling, see rails configuration guide
  # http://guides.rubyonrails.org/configuring.html#database-pooling
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>

development:
  <<: *default
  database: sample_articles_development
  username: rails
  password: *******
  host: localhost
  port: 5432

test:
  <<: *default
  database: sample_articles_test

production:
  <<: *default
  database: sample_articles_production
  username: sample_articles
  password: <%= ENV['SAMPLE_ARTICLES_DATABASE_PASSWORD'] %>

Only rake db:create will try to create a new database. rake db:migrate will use an existing one (which it reads from database.yml). You refer to calling rake db:create as "doing a migration". it isn't - you're just confusing things. — Max Williams
– Max Williams, Commented Apr 12, 2016 at 11:27
Ok. Maybe confusing. I'm completely new to Rails. Ok, lets say the problem is in db:migrate. But still the prob is that i can't understand why does it use one of my existing DB's — user1935987
– user1935987, Commented Apr 12, 2016 at 11:30
Well then your question becomes "When i'm running db:migrate Rails is trying to manipulate my existing DB's", and this is the expected behaviour, so there's nothing wrong. — Max Williams
– Max Williams, Commented Apr 12, 2016 at 11:31
why is this expected behavior? i do set a DB name in my database.yml — user1935987
– user1935987, Commented Apr 12, 2016 at 11:32

SteveTurczyn · Accepted Answer · 2016-04-12 12:37:17Z

1

You likely have a $DATABASE_URL variable in your environment. That will override the value in database.yml.

unset DATABASE_URL

answered Apr 12, 2016 at 12:37

SteveTurczyn

37k6 gold badges46 silver badges56 bronze badges

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

1 Comment

user1935987 Over a year ago

Yep, that was the problem. Thank you, didn't thought about this case.

Collectives™ on Stack Overflow

Rails db:migrate / db:create. Existed databases conflict

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related