[TheEmpty]

ShanePerreault, on 18 September 2011 - 06:37 PM, said:

I'm having trouble using the 'pg' gem in my rails application. I want to use MySQL but am on the free plan right now? Anyone else ever had problems using the 'pg' gem and heroku? Assistance needed. Trying to launch CSS-labs pre-beta.

pg = PostgreSQL, what their DBs are. I have no idea if you can use MySQL, but what you can do is:

gem 'mysql', :group => [:development, :test]
gem 'pg', :group => [:production]

but you'll want to run your test suite against it for PG SQL errors, etc. so best to switch, it is much faster with AR anyways.

[ShanePerreault]

ThatRailsGuy, on 18 September 2011 - 06:46 PM, said:

pg = PostgreSQL, what their DBs are. I have no idea if you can use MySQL, but what you can do is:

gem 'mysql', :group => [:development, :test]
gem 'pg', :group => [:production]

but you'll want to run your test suite against it for PG SQL errors, etc. so best to switch, it is much faster with AR anyways.

I understand it's a PostgreSQL database, and I'm using ActiveRecord. I just can't figure how to a) get my db info from heroku b) run the migrations and c) connect.

[TheEmpty]

ShanePerreault, on 18 September 2011 - 07:34 PM, said:

I understand it's a PostgreSQL database, and I'm using ActiveRecord. I just can't figure how to a) get my db info from heroku b) run the migrations and c) connect.

heroku rake db:migrate
heroku rake db:pull

http://blog.heroku.c...nd_from_heroku/

[gushort]

You would probably be using the pg gem only for production, and the mysql one locally for development, so be sure to put the sql gem in a development/test group and the pg one into a production group:

group :development, :test do
  gem 'mysql2', '<= 0.2.9'
end

group :production do
  gem pg
end

As for connecting to your db in Heroku, you can't access a Heroku shared db's data remotely. Not easily anyway.

If it is just populating your db with initial records that you're concerned about, then you would probably just use the db/seeds.rb file for that.

[gushort]

You may also want to have a look at Taps for pushing and pulling data from your Heroku db.

[ShanePerreault]

gushort, on 18 September 2011 - 08:54 PM, said:

You would probably be using the pg gem only for production, and the mysql one locally for development, so be sure to put the sql gem in a development/test group and the pg one into a production group:

group :development, :test do
  gem 'mysql2', '<= 0.2.9'
end

group :production do
  gem pg
end

As for connecting to your db in Heroku, you can't access a Heroku shared db's data remotely. Not easily anyway.

If it is just populating your db with initial records that you're concerned about, then you would probably just use the db/seeds.rb file for that.

I'm mainly talking about populating my database.yml file.

[TheEmpty]

gushort, on 18 September 2011 - 08:54 PM, said:

You would probably be using the pg gem only for production, and the mysql one locally for development, so be sure to put the sql gem in a development/test group and the pg one into a production group:

group :development, :test do
  gem 'mysql2', '<= 0.2.9'
end

group :production do
  gem pg
end

As for connecting to your db in Heroku, you can't access a Heroku shared db's data remotely. Not easily anyway.

If it is just populating your db with initial records that you're concerned about, then you would probably just use the db/seeds.rb file for that.

Don't use different dbs, NEVER! PG has different JOINs, etc. so if you won't get those errors in production, use it in development and testing so you get those errors earlier in the stage.

[gushort]

ThatRailsGuy, on 19 September 2011 - 11:40 AM, said:

Don't use different dbs, NEVER! PG has different JOINs, etc. so if you won't get those errors in production, use it in development and testing so you get those errors earlier in the stage.

Thanks for the "heads up". I've been using MySQL, as it is what seemed to be the standard, but Heroku uses PG, so I've been installing PG onto my system (what a pain - even with Homebrew), and intend to stick with that.

[Mo3]

gushort, on 07 October 2011 - 11:46 AM, said:

Thanks for the "heads up". I've been using MySQL, as it is what seemed to be the standard, but Heroku uses PG, so I've been installing PG onto my system (what a pain - even with Homebrew), and intend to stick with that.

You don't have to install PG, Rails will automatically use SQLite if you don't have it.

[TheEmpty]

Homebrew makes that stuff really easy though it has been a long time since I've used it.

Mo3, on 07 October 2011 - 01:21 PM, said:

You don't have to install PG, Rails will automatically use SQLite if you don't have it.

1) It's not automatic
2) please see convo

[gushort]

Mo3, on 07 October 2011 - 01:21 PM, said:

You don't have to install PG, Rails will automatically use SQLite if you don't have it.

I wanted to install it anyway, so I could easily access data in my Heroku backups.

[Daniel15]

Quote

You would probably be using the pg gem only for production, and the mysql one locally for development,

If you knew that your live server would be using PostgreSQL, why would you be using MySQL for development? Surely it'd be a lot easier to use PostgreSQL for both?

Quote

Thanks for the "heads up". I've been using MySQL, as it is what seemed to be the standard, but Heroku uses PG, so I've been installing PG onto my system (what a pain - even with Homebrew), and intend to stick with that.

MySQL and PostgreSQL are both very commonly used. I'd say that PostgreSQL is better as it's more powerful, but it is harder to set up. Its support for stored procedures is significantly better than that of MySQL, for one. Stored procs are very important for large systems.