On Mar 22, 3:30 pm, "Robert R." <li...@ruby-forum.com> wrote: > I have the same problems under Mac OS X Leopard. I am using ruby > 1.9.2p180, Rails 3.0.5, rake 0.8.7 and gem 1.5.9. I installed > postgres-pr, but after a rake db:migrate I got this message: > > rake aborted! > no such file to load -- pg > /opt/local/lib/ruby1.9/gems/1.9.1/gems/activesupport-3.0.5/lib/active_suppo > rt/dependencies.rb:239:in > `require' > /opt/local/lib/ruby1.9/gems/1.9.1/gems/activesupport-3.0.5/lib/active_suppo > rt/dependencies.rb:239:in > `block in require' > /opt/local/lib/ruby1.9/gems/1.9.1/gems/activesupport-3.0.5/lib/active_suppo > rt/dependencies.rb:225:in > `block in load_dependency' > /opt/local/lib/ruby1.9/gems/1.9.1/gems/activesupport-3.0.5/lib/active_suppo > rt/dependencies.rb:596:in > `new_constants_in' > /opt/local/lib/ruby1.9/gems/1.9.1/gems/activesupport-3.0.5/lib/active_suppo > rt/dependencies.rb:225:in > `load_dependency' > /opt/local/lib/ruby1.9/gems/1.9.1/gems/activesupport-3.0.5/lib/active_suppo > rt/dependencies.rb:239:in > `require' > > And this command here > > rake rails:update > > does not solve my problem. I am still unable to execute rake db:migrate. > But the command > > rails dbconsole > > works fine. Any ideas what's going on? >
rails dbconsole just fires up the database's native command line tool, using database.yml to pull out the host and so on, so it will worked even if the gem used for that database is missing etc. The gem used for postgres these days is called pg - make sure that is in your Gemfile (and of course run bundle install after modifying your Gemfile) Fred -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
