Peter Vandenabeele wrote in post #969187: > Michael Satterwhite wrote in post #969184: >> Peter Vandenabeele wrote in post #969183: >>> >>> Ah, thanks for that info. >>> It works that way here too. >>> >>> pet...@asus:~$ export RUBYOPT=rubygems >>> pet...@asus:~$ echo $RUBYOPT >>> rubygems >>> pet...@asus:~$ irb >>> irb(main):001:0> require 'pg' >>> => true >>> irb(main):002:0> Object.constants.grep(/PG/) >>> => ["PGconn", "PGresult", "PGError"] >>> >> >> Actually, yours works much better ... mine isn't working, remember. <g> >> >> Any idea of how I can find where that bogus 'pg' is coming from? The gem >> isn't installed anymore, but "require 'pg'" still returns true - loading >> no constants. > > Aha, this might hint where your seemingly > succeeded require is getting its input ? > After the require, the $LOAD_PATH has grown ! > THANK YOU, THANK YOU, THANK YOU!!!!
This piece led me to a rogue gem that I'd installed when I was trying to get started. The require 'pg' is now giving the proper results and the test rake db:migrate connects to the database. I *REALLY* appreciate this! ---Michael -- Posted via http://www.ruby-forum.com/. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
