rake db:create throws “database does not exist” error with postgresql

Question

I'm using rails 5.2.2.1 with postgresql 10.6, and I'm not able to create a database in my development environment. When I run

bin/rake db:create

or

bundle exec rake db:create

I get

rake aborted!
ActiveRecord::NoDatabaseError: FATAL:  database "mplaces_dev" does not exist
/home/user/.rvm/gems/ruby-2.5.3/gems/activerecord-5.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:696:in `rescue in connect'
/home/user/.rvm/gems/ruby-2.5.3/gems/activerecord-5.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:691:in `connect'

I am trying to create the database so, naturally, it does not exist. However rails should create it ... Here's my config/database.yml:

development:
 adapter: postgis
 database: mplaces_dev
 encoding: unicode
 username: postgres
 password: postgres
 host: localhost
 postgis_extension: true
 schema_search_path: "public,postgis"

However I also created all the extensions. I've been at this for more than an hour, and still can't understand why this is happening ...

Thanks!

did you installed postgres in you're system? & pg gem in you're application — uday
– uday, Commented Apr 22, 2019 at 9:29
Yes, by this command bin/rake db:create RAILS_ENV=development. — code_aks
– code_aks, Commented Apr 22, 2019 at 9:36
you're adapter name is incorrect postgis change this to postgresql — uday
– uday, Commented Apr 22, 2019 at 9:37

Aymen Bou · Accepted Answer · 2021-04-18 15:33:36Z

5

For me, it was because I had some Model dependant logic in one of my initializers.

This was never a problem before, but since setting up CI, I need to modify my project so that it excludes some logic from the initializers for the Model dependent part.

For initializer_example.rb:

# non model dependent
Aws.config(secret_key: xyz, access_key: zyx)

# model dependent
User.where(admin:true).update(field: value)

To:

# non model dependent
Aws.config(secret_key: xyz, access_key: zyx)

# model dependent
db_loaded = ::ActiveRecord::Base.connection_pool.with_connection(&:active?) rescue false
if db_loaded
    User.where(admin:true).update(field: value)
end

This will run the initializer as usual ONLY if the database has been loaded (i.e in production)

As for my CI/Testing environments, I modify the RSPEC's to load the initializer again (bad practice I know) before testing (of course by this stage the environment should be configured so this time it will run as normal) using the code:

load "#{Rails.root}/config/initializers/initializer_example.rb"

answered Apr 18, 2021 at 15:33

Aymen Bou

1,1271 gold badge14 silver badges24 bronze badges

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

2 Comments

Max Pekarsky Over a year ago

Thank you so much! I googled for an hour before I found this solution. I also created a custom initializer to load some data. When I moved to a different machine, rake db:create failed. Commenting out the Model.create calls fixed this.

jakeonfire Over a year ago

ActiveRecord::Base.connected? works for me.

Collectives™ on Stack Overflow

rake db:create throws “database does not exist” error with postgresql

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related