X-Original-To: pgsql-hackers@postgreSQL.org
Received: from mosca.csse.monash.edu.au (mosca.csse.monash.edu.au
	[130.194.64.67]) by postgresql.org (Postfix) with ESMTP
	id C745F475FC8; Mon, 10 Mar 2003 16:34:03 -0500 (EST)
Received: from freaky-namuh.com (zephyrus.csse.monash.edu.au
 [130.194.224.223])
	by mosca.csse.monash.edu.au (8.11.6+Sun/8.10.2) with ESMTP id
	h2ALXwA12065; Tue, 11 Mar 2003 08:33:58 +1100 (EST)
Message-ID: <3E6D0598.9060503@freaky-namuh.com>
Date: Tue, 11 Mar 2003 08:37:28 +1100
From: Ashley Cambrell <ash@freaky-namuh.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.3b) Gecko/20030101
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
Subject: Re: Roadmap for FE/BE protocol redesign
References: <19041.1047322279@sss.pgh.pa.us>
In-Reply-To: <19041.1047322279@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200303/383
X-Sequence-Number: 36629

Tom Lane wrote:

>This is an attempt to lay out a road map for updating the frontend/backend
>protocol in 7.4.  I don't at this point want to get into details on any
>one of the TODO items, just get consensus that this is the set of tasks
>to be tackled.  Are there any areas that I've missed (that require
>protocol changes)?
>
>  
>
What about binding variables ala oracle's ociparse -> ocibindbyname -> 
ociexecute -> ocifetch ?  I know you can do most of it via SQL 
(PREPARE/EXECUTE) but you can't do 'RETURN x INTO :x' as it stands.  
This would also get around the problem of getting values from newly 
inserted rows (eg PKs) without resorting to OIDs.  Not entirely a FE/BE 
issue... but worth considering in any redesign.

Ashley Cambrell