Just followed the "Migrating to PostgreSQL" Railscast, migrating my local sqlite3 database to postgres:
here is my database.yml file:
development:
adapter: postgresql
encoding: unicode
database: app_development
pool: 5
host: localhost
username: martinbraun
password:
test:
adapter: postgresql
encoding: unicode
database: app_test
pool: 5
username: mbraun
password:
production:
adapter: postgresql
encoding: utf8
database: app_production
pool: 5
username: mbraun
password:
My postgres server is running on postgressapp on port 5432. It tells me that it's running and I get connection to my database app_development.
However, "which psql" tells me:
/usr/bin/psql
and when I start my app, all the records are not loading, I simply see my application layout and all html stuff which is not related to any records. No error is showing up.
I have verified that my database contains data via rails console, so the migration from sqlite3 to postgres was def successful. I am just wondering why my records are not showing and what I do wrong here?
Related
Recently try Rails 6 feature for multiple database :
With database.yml like this
development:
primary:
adapter: postgresql
encoding: unicode
username: hoho
password: hoho
host: X.X.X.X
port: 5432
pool: 5
database: hoho_development
secondary:
adapter: postgresql
encoding: unicode
username: haha
password: haha
host: Y.Y.Y.Y
port: 5432
pool: 5
database: haha_development
migrations_paths: db/secondary_migrate
although db/secondary_migrate is empty..when i execute rails db:migrate, it still write ar_internal_metadata and schema_migrations.
is there any way to avoid this? in my usecase i don't want to write any new table to the second database, just want to read and write to existing tables that created not from rails migration.
How can I make the database records that I have on my heroku app to be available also on my machine?
database.yml
development:
adapter: sqlite3
encoding: unicode
database: databasename
pool: 5
username: my_mac_username
password: #no password filled
test:
adapter: sqlite3
encoding: unicode
database: testdatabasename
pool: 5
username: my_mac_username
password: #no password filled
production:
adapter: postgresql
encoding: unicode
database: productiondatabasename
pool: 5
username: my_mac_username
password: #no password filled
I run
heroku pg:pull DATABASE_URL productiondatabasename --app my_heroku_app_name
and bunch of lines is being displayed in my terminal. But that's it. Nothing more happens. I still do not have the records available on localhost.
What am I missing here?
What I was doing wrong was the configuration of database.yml.
If using sqlite3, drop your db first, then change the development adapter to postgresql (make sure that you have installed it properly!). Then recreate the database.
After running
heroku pg:pull DATABASE_URL developmentdatabasename --app my_heroku_app_name
everything should be OK!
I updated my database.yml file to look like so:
test:
adapter: postgresql
encoding: unicode
database: startpoint_test
hostname: localhost
pool: 5
username: postgres
password: password
development:
adapter: postgresql
encoding: unicode
database: startpoint_dev
pool: 5
username: postgres
password: password
And now it seems when I run my application, and sign up a new user the development database does not get a new user inserted into it ...
The tests all pass for signing up a new user
Have you tried using
rake db:create:all
and then
rake db:test:prepare
I am in the process of migrating my SQL to Postgresql because I want to develop in the same environment as my production.
I installed Postgres and was able to set my database yml file such that rake db:create:all worked with no problems.
However before I pushed, I realized that the username and password of the postgresql database is only available on my computer. I.e. I created the login role on my computer. When my friend who is also developing on the application, pulls the code, he won't have the username and password created by me on my computer.
Is he supposed to also create the same login role? Or is there a way to leave username / password blank so that everyone who develops can access the application? More importantly, what is the best practice for a situation like this?
I am developing on windows and he is on mac.
My database.yml: username and password left out.
development:
adapter: postgresql
encoding: unicode
database: volatility_development
pool: 5
timeout: 5000
host: localhost
test:
adapter: postgresql
encoding: unicode
database: volatility_test
pool: 5
timeout: 5000
host: localhost
production:
adapter: postgresql
encoding: unicode
database: volatility_production
pool: 5
timeout: 5000
one possibility would be to use a combination of erb and environment variables, for example:
development:
username: <%= ENV['USERNAME'] %>
password: <%= ENV['PASSWORD'] %>
adapter: postgresql
encoding: unicode
database: volatility_development
pool: 5
timeout: 5000
host: localhost
then you could do either of the following:
start your server like so: USERNAME=bob PASSWORD=secret rails s
add the following to your .bashrc
export USERNAME=bob
export PASSWORD=secret
It it possible to use the JDBC Postgres (jRuby) driver without specifying a username and password in the database.yml file? My project database file currently is:
test: &test
adapter: postgresql
encoding: unicode
database: app_test
pool: 5
development: &development
adapter: postgresql
encoding: unicode
database: app_development
pool: 5
production: &production
adapter: postgresql
encoding: unicode
database: app_production
pool: 5
cucumber:
<<: *test
However, this causes the following error on starting the server / console:
ActiveRecord::JDBCError: The driver encountered an unknown error: FATAL: no PostgreSQL user name specified in startup packet
If possible, it would be nice to not include the username and password out of the database.yml configuration file (this works with MRI and the pg gem). Each team members uses a different username for their local installs.