From: Bruce Momjian <maillist@candle.pha.pa.us>
To: lockhart@alumni.caltech.edu
Cc: meskes@usa.net
Cc: pgsql-hackers@hub.org
Subject: Re: [HACKERS] PREPARE
Date: Tue, 17 Nov 1998 11:16:52 -0500 (EST)
Message-ID: <199811171616.LAA09176@candle.pha.pa.us> (raw)
In-Reply-To: <36517DEF.7989C4EC@alumni.caltech.edu>
> > 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
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: maillist@candle.pha.pa.us, lockhart@alumni.caltech.edu, meskes@usa.net, pgsql-hackers@hub.org
Subject: Re: [HACKERS] PREPARE
In-Reply-To: <199811171616.LAA09176@candle.pha.pa.us>
* 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