DISQUS

Josh Kim dot Org: PostgreSQL, Ruby, and Rails: I Quit

  • Robby Russell · 1 year ago
    Hey there... sorry to hear that you had some troubles. I am planning to post a new version of my post shortly. Here are some of my notes from doing a full install last week with my new MacBook Pro.

    * http://gist.github.com/17502

    Good luck!
  • Robby Russell · 1 year ago
    Hey there... sorry to hear that you had some troubles. I am planning to post a new version of my post shortly. Here are some of my notes from doing a full install last week with my new MacBook Pro.


    * http://gist.github.com/17502



    Good luck!
  • Carl Pelletier · 1 year ago
    If that can help, I find the solution for ruby-pg. You must specify the adapter in config/database.yml at:
    adapter:postgresql

    That it! No more complain by Activerecord...

    Thanks
  • ehsanul · 1 year ago
    You're wrong Carl. I saw this "solution" as well online (I'm having the same problem), and I did originally have it set to "postgres", which was wrong. But even after changing it to "postgresql", I get the same type of error. Actually, with adapter set to postgres, I get this error:

    "Please install the postgres adapter: `gem install activerecord-postgres-adapter` (no such file to load -- active_record/connection_adapters/postgres_adapter)"

    When it's set correct to "postgresql", I get this error:

    Please install the postgresql adapter: `gem install activerecord-postgresql-adapter` (no such file to load -- pg)

    I've tried both the ruby-pg and postgres gems, to no avail. Any help would be appreciated.
  • joshkim · 1 year ago
    Did you try the gist that robby posted? I haven't had a chance to, but
    it looks like it *may* work.

    My solution was just to go MySQL and worry about integration with
    PostgreSQL later, or maybe have that magic happen on the production
    server, which has Ubuntu installed.
  • Carl Pelletier · 1 year ago
    If that can help, I find the solution for ruby-pg. You must specify the adapter in config/database.yml at:
    adapter:postgresql



    That it! No more complain by Activerecord...



    Thanks
  • James Nachbar · 1 year ago
    Take a look at my comments here:

    http://nachbar.name/blog/2008/11/28/rails-and-p...
  • ehsanul · 1 year ago
    You're wrong Carl. I saw this "solution" as well online (I'm having the same problem), and I did originally have it set to "postgres", which was wrong. But even after changing it to "postgresql", I get the same type of error. Actually, with adapter set to postgres, I get this error:


    "Please install the postgres adapter: `gem install activerecord-postgres-adapter` (no such file to load -- active_record/connection_adapters/postgres_adapter)"



    When it's set correct to "postgresql", I get this error:



    Please install the postgresql adapter: `gem install activerecord-postgresql-adapter` (no such file to load -- pg)



    I've tried both the ruby-pg and postgres gems, to no avail. Any help would be appreciated.
  • joshkim · 1 year ago
    Did you try the gist that robby posted? I haven't had a chance to, but
    it looks like it *may* work.



    My solution was just to go MySQL and worry about integration with

    PostgreSQL later, or maybe have that magic happen on the production

    server, which has Ubuntu installed.
  • ehsanul · 1 year ago
    Thanks for the reply joshkim.


    Well, all that's being done there in the gist to do with this is "sudo gem install postgres", which is sorta obvious. I don't think the problem is with the gem, though I've tried uninstalling and installing a few times, and tried the other ruby-pg gem too. Robby doesn't have the same error I do. The error shows up when doing a rake command to create the database, and occurs for others when trying a rake db migration command.



    I think this error only shows up with the latest rails, because I've been using postgresql on my laptop with rails 2.1.1 for a while. But it messes up on my server, which has rails 2.2.2 installed. The problem doesn't seem to be with the gem, but with activerecord itself. I don't know nearly enough about rails to begin trying to solve it though.



    I guess I may switch to mysql for now myself, just to get things working, but that isn't really a solution to me.
  • joshkim · 1 year ago
    Yeah, same here. I started poking around in rails to see how I could
    fix it, but I gave up after gobs and gobs of time spent on it. I also

    remember it working in 2.1, because I was working on another rails

    project back then... but something must have changed with 2.2.
  • Mustafa · 1 year ago
    i got this setup working


    postgres 8.3.5

    nb 6.5 ruby

    postgres-pr 0.5.0



    there are instructions on a blog on the dzone site, by some indian guy, it definitely works



    you need to create the db before working with it from nb, once its created, migrations do work, but for some reason the inital create:db doesnt work.
  • thooby · 1 year ago
    Mustafá, I woud like to find the 'blog on the dzone site, by some indian guy' Could you tel us the url
  • Orhino · 1 year ago
    Yeah Mustafa.. the url would've been a cool addition to your comment..
  • Mustafa · 1 year ago
    you folks want to be spoon-fed, hmmm i dunno, here you go


    http://blogs.sun.com/jkshah/entry/postgresql_an...
  • Mustafa · 1 year ago
    argh thats what i get for rushing my reply


    heres the correct url



    http://netbeans.dzone.com/news/rails-and-postgr...
  • John Mileham · 10 months ago

    I've done a couple of rails installs now on laptops and found myself in the exact same situation as you when installing on a new box -- real headscratcher. My problem was this: I'd installed rubygems via macports but neglected to install a fresh copy of rake via rubygems, which meant that when doing a rake db:migrate, it would find OS X's native rubygems. I only figured this out because script/server (which relies on the ruby binary) was working where rake was not.


    A 'gem install rake' (and a new terminal window to clear the bash path cache -- try saying that out loud) fixed me right up.


    If this command doesn't return three binaries in the same directory for you, you might be in the same boat:


    $ which ruby rake gem


    -john