Received: from golem.jpl.nasa.gov (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.1/8.9.1) with ESMTP id IAA12886 for ; Tue, 17 Nov 1998 08:45:28 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id NAA24108; Tue, 17 Nov 1998 13:45:20 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <36517DEF.7989C4EC@alumni.caltech.edu> Date: Tue, 17 Nov 1998 13:45:19 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: Michael Meskes CC: pgsql-hackers@hub.org Subject: Re: [HACKERS] PREPARE References: <000501be119e$6c16efa0$8a14f7d0@taral.dobiecenter.com> <19981117101824.C2181@usa.net> 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 - 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