Subject: Re: ruby-postgres for Ruby 1.9
From: Jeff Davis <pgsql@j-davis.com>
To: Chris Long <galizur@gmail.com>
Cc: pgsql-interfaces@postgresql.org
In-Reply-To: <1172664325.709947.125810@p10g2000cwp.googlegroups.com>
References: <1172664325.709947.125810@p10g2000cwp.googlegroups.com>
Content-Type: text/plain
Date: Thu, 01 Mar 2007 13:32:27 -0800
Message-Id: <1172784747.13722.106.camel@dogma.v10.wvs>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2007-02-28 at 04:05 -0800, Chris Long wrote:
> It looks like ruby-postgres needs some patching due to the changes
> in rubyio.h.  I believe these two changes take care of the problem:
> 
>     /*    PQtrace(get_pgconn(obj), fp->f2?fp->f2:fp->f); */
>     PQtrace(get_pgconn(obj), fp->stdio_file);
> 
>     /*    PQprint(fp->f2?fp->f2:fp->f, get_pgresult(obj), &po);*/
>     PQprint(fp->stdio_file, get_pgresult(obj), &po);
> 
> I'm using the force a bit here, and assuming that the additional
> pointer for rw pipes has been deprecated.   In my defense it compiles
> and runs.
> 
> Who's the current maintainer of ruby-postgres?

[I see that this is a cross post with ruby-talk, so I'm pasting my
answer here also]

Dave Lee is the current maintainer, dave@cherryville.org, and I have
quite a few fixes that I'd like applied as well. He's been busy for the
past few months, so I haven't had much luck getting the fixes in. He's
supposed to be giving me read access to the repository so I can at least
see what he's committing to it, but I've been waiting on that for a
while, too.

Overall, the module needs a substantial amount of work (it's still using
deprecated API functions, for instance).

Regards,
        Jeff Davis

PS: He has another email address also, but I don't want to post that on
a public list because I haven't seen it in other public lists/sites.