View Single Post

   
  #18 (permalink)  
Old 04-16-2008, 01:00 AM
Heikki Linnakangas
 
Posts: n/a
Default Re: Retrieving last InsertedID : INSERT... RETURNING safe ?

Paul Tomblin wrote:
> Be that as it may, I still don't see what you gain by doing
> insert ... (nextval('idseq'),...
> select currval('idseq');
> when you could do
> select nextval('idseq');
> insert ...(?,...


Oh, sure, there's not gain either way. Select nextval + insert works
just as well.

Theoretically, you could "pipeline" the "INSERT nextval" + "SELECT
currval" method, by sending both commands at once and only then block
and wait for response, saving one round-trip to the server. You could do
that with a batch statement, I think, or by single executeQuery("INSERT
.... ; SELECT currval(...)"). But if you don't do that, there's no
difference.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Reply With Quote