Thread: PG_COMMAND_OK oid information required

<div id="RTEContent">Hi,<br /><br /> Would it be possible to provide more information in the PGResult object (or rather
itsassociated functions) about operations that don't return a value of PG_RESULT_OK.  Specifically, I believe, it would
beuseful for clients to know the oid's of values being inserted or updated.  <br /><br /> That way, if it realizes
thereare many similar operations to carry out, it would be easier to use PQExecParams.  The only way I can see of doing
thiscurrently would be to issue a <br /><br /> select <cols to insert><br /> from table<br /> limit 1<br /><br />
toget the oids, and then prepare the insert statement using the info retrieved from the select.  Am I missing
something? Would a patch with this change be considered?<br /><br /> Thanks,<br /> Andy Chambers<br /></div><p><hr
size="1"/><font face="Verdana, Arial, Helvetica, sans-serif" size="2"><a
href="http://us.rd.yahoo.com/mail/uk/taglines/default/messenger/*http://uk.messenger.yahoo.com
 
">Yahoo! Messenger</a> <font color="red">NEW</font> - crystal clear PC to PC <a
href="http://us.rd.yahoo.com/mail/uk/taglines/default/messenger/*http://uk.messenger.yahoo.com
 
">calling worldwide with voicemail </a></font>

Andy Chambers <andychambers2002@yahoo.co.uk> writes:
>  Would it be possible to provide more information in the PGResult object (or rather its associated functions) about
operationsthat don't return a value of PG_RESULT_OK.  Specifically, I believe, it would be useful for clients to know
theoid'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