pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ashley Cambrell <ash@freaky-namuh.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Tue, 11 Mar 2003 08:37:28 +1100
Message-ID: <3E6D0598.9060503@freaky-namuh.com> (raw)
In-Reply-To: <19041.1047322279@sss.pgh.pa.us>
References: <19041.1047322279@sss.pgh.pa.us>

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





view thread (133+ messages)  latest in thread

Message-ID: <3E6D0598.9060503@freaky-namuh.com>
Permalink:  ../3E6D0598.9060503@freaky-namuh.com/
Also on:    postgresql.org/message-id/3E6D0598.9060503@freaky-namuh.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: ash@freaky-namuh.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
  Subject: Re: Roadmap for FE/BE protocol redesign
  In-Reply-To: <3E6D0598.9060503@freaky-namuh.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