Re: PG_COMMAND_OK oid information required

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andy Chambers <andychambers2002(at)yahoo(dot)co(dot)uk>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PG_COMMAND_OK oid information required
Date: 2005-11-27 22:51:20
Message-ID: 7573.1133131880@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Andy Chambers <andychambers2002(at)yahoo(dot)co(dot)uk> writes:
> Would it be possible to provide more information in the PGResult object (or rather its associated functions) about operations that don't return a value of PG_RESULT_OK. Specifically, I believe, it would be useful for clients to know the oid's of values being inserted or updated.

Huh? What oids exactly? There's no such thing as PG_RESULT_OK, so
you're far from making yourself clear.

> Would a patch with this change be considered?

If I understand what you are after at all, it would involve a protocol
change, which means the bar is a whole lot higher than "it'd be nice".

regards, tom lane

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message Eugene Prokopiev 2005-11-28 05:49:32 Re: pl/pyton: exceptions.ImportError: No module named
Previous Message Andy Chambers 2005-11-27 20:19:07 PG_COMMAND_OK oid information required