pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andy Chambers <andychambers2002@yahoo.co.uk>
To: pgsql-interfaces@postgresql.org
Subject: PG_COMMAND_OK oid information required
Date: Sun, 27 Nov 2005 20:19:07 +0000 (GMT)
Message-ID: <20051127201907.67266.qmail@web26910.mail.ukl.yahoo.com> (raw)

Hi,
 
 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.  
 
 That way, if it realizes there are many similar operations to carry out, it would be easier to use PQExecParams.  The only way I can see of doing this currently would be to issue a 
 
 select <cols to insert>
 from table
 limit 1
 
 to get 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?
 
 Thanks,
 Andy Chambers
 

		
---------------------------------
Yahoo! Messenger  NEW - crystal clear PC to PC calling worldwide with voicemail 

view thread (2+ messages)  latest in thread

Message-ID: <20051127201907.67266.qmail@web26910.mail.ukl.yahoo.com>
Permalink:  ../20051127201907.67266.qmail@web26910.mail.ukl.yahoo.com/
Also on:    postgresql.org/message-id/20051127201907.67266.qmail@web26910.mail.ukl.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: andychambers2002@yahoo.co.uk
  Subject: Re: PG_COMMAND_OK oid information required
  In-Reply-To: <20051127201907.67266.qmail@web26910.mail.ukl.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox