Re: new RETURNING clause and Pg.pm

From: "Brandon Metcalf" <bmetcalf(at)nortel(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: new RETURNING clause and Pg.pm
Date: 2008-06-26 17:24:51
Message-ID: Pine.LNX.4.58L.0806261224210.9186@cash.us.nortel.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

t == tgl(at)sss(dot)pgh(dot)pa(dot)us writes:

t> "Brandon Metcalf" <bmetcalf(at)nortel(dot)com> writes:
t> > I just upgraded to 8.3.3 and taking advantage of the RETURNING clause
t> > which is really cool. I've found that with Pg.pm $r->resultStatus
t> > returns the integer "2" when the RETURNING clause is used on an
t> > insert.

t> > Of course, without using RETURNING the status is the constant
t> > PGRES_COMMAND_OK.

t> Sounds to me like a bug in Pg.pm --- it's probably not expecting
t> a result to come back from an INSERT. You oughta nag its author
t> about that.

I'll look through the Pg.pm code and see what I can find.

--
Brandon

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Shulman 2008-06-26 17:47:04 Re: what are rules for?
Previous Message rob 2008-06-26 17:20:58 libpq block allocated before my malloc handler inits?