To: Neil Conway <neilc@samurai.com>
Cc: Ashley Cambrell <ash@freaky-namuh.com>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	pgsql-interfaces@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign 
In-reply-to: <1047333552.357.286.camel@tokyo> 
References: <19041.1047322279@sss.pgh.pa.us>
	<3E6D0598.9060503@freaky-namuh.com>
	<1047333552.357.286.camel@tokyo>
Comments: In-reply-to Neil Conway <neilc@samurai.com>
	message dated "10 Mar 2003 16:59:12 -0500"
Date: Mon, 10 Mar 2003 17:06:00 -0500
Message-ID: <20429.1047333960@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Neil Conway <neilc@samurai.com> writes:
> On Mon, 2003-03-10 at 16:37, Ashley Cambrell wrote:
>> This would also get around the problem of getting values from newly 
>> inserted rows (eg PKs) without resorting to OIDs.

> That's not a problem: ensure that the newly inserted row has a SERIAL
> column, and use currval().

There was some talk awhile back of inventing INSERT ... RETURNING and
UPDATE ... RETURNING commands so that you could pass back computed
values to the frontend without an extra query.  It doesn't seem to have
gotten further than a TODO item yet, though.  AFAICS this does not need
a protocol extension, anyway --- it'd look just the same as a SELECT
at the protocol level.

			regards, tom lane