From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199811171616.LAA09176@candle.pha.pa.us>
Subject: Re: [HACKERS] PREPARE
In-Reply-To: <36517DEF.7989C4EC@alumni.caltech.edu> from "Thomas G. Lockhart"
	at "Nov 17, 1998  1:45:19 pm"
To: lockhart@alumni.caltech.edu (Thomas G. Lockhart)
Date: Tue, 17 Nov 1998 11:16:52 -0500 (EST)
Cc: meskes@usa.net, pgsql-hackers@hub.org
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> > I'm still holding back PREPARE for ecpg until I can think of a
> > good solution. The best of course would be in the backend.
> 
> So what would it take to do this in the backend? I think the places
> which would need to be touched fall into areas I either know about or am
> starting to look at to implement the CASE clause.
> 
> We'd need:
>   - a "named buffer" (or several) to hold the intermediate input

portals

>   - a way to pass in parameters or substitution arguments

SQL functions?

>   - a way to decide if previous parser/planner/executor
>     results can be reused


-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026