Re: Retrieving last InsertedID : INSERT... RETURNING safe ? - Mailing list pgsql-jdbc

From Heikki Linnakangas
Subject Re: Retrieving last InsertedID : INSERT... RETURNING safe ?
Date
Msg-id 47BC387D.60008@enterprisedb.com
Whole thread Raw
In response to Re: Retrieving last InsertedID : INSERT... RETURNING safe ?  ("Paul Tomblin" <ptomblin@gmail.com>)
List pgsql-jdbc
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

pgsql-jdbc by date:

Previous
From: "Paul Tomblin"
Date:
Subject: Re: Retrieving last InsertedID : INSERT... RETURNING safe ?
Next
From: Kris Jurka
Date:
Subject: Re: extra rowcopy in ResultSet allways needed ?.