From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: Michael Meskes <meskes@usa.net>
Cc: pgsql-hackers@hub.org
Subject: Re: [HACKERS] PREPARE
Date: Tue, 17 Nov 1998 13:45:19 +0000
Message-ID: <36517DEF.7989C4EC@alumni.caltech.edu> (raw)
References: <000501be119e$6c16efa0$8a14f7d0@taral.dobiecenter.com>
<19981117101824.C2181@usa.net>
> 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
- a way to pass in parameters or substitution arguments
- a way to decide if previous parser/planner/executor
results can be reused
What else?
- Tom
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: lockhart@alumni.caltech.edu, meskes@usa.net, pgsql-hackers@hub.org
Subject: Re: [HACKERS] PREPARE
In-Reply-To: <36517DEF.7989C4EC@alumni.caltech.edu>
* 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