Received: from golem.jpl.nasa.gov (IDENT:root@hectic-2.jpl.nasa.gov
	[128.149.68.204]) by hub.org (8.9.1/8.9.1) with ESMTP id WAA10100
	for <pgsql-hackers@hub.org>; Wed, 18 Nov 1998 22:33:06 -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 DAA04253;
	Thu, 19 Nov 1998 03:32:54 GMT
Sender: tgl@mythos.jpl.nasa.gov
Message-ID: <36539166.A9FEAA7E@alumni.caltech.edu>
Date: Thu, 19 Nov 1998 03:32:54 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Organization: Caltech/JPL
X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.30 i686)
MIME-Version: 1.0
To: Michael Meskes <meskes@usa.net>
CC: pgsql-hackers@hub.org
Subject: Re: [HACKERS] PREPARE
References: <000501be119e$6c16efa0$8a14f7d0@taral.dobiecenter.com>
	<19981117101824.C2181@usa.net>
	<36517DEF.7989C4EC@alumni.caltech.edu>
	<19981117203009.E1442@usa.net>
	<36523DB2.BF0984CA@alumni.caltech.edu>
	<19981118084843.B869@usa.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> But wouldn't it be more useful to preprocess the query and store the
> resulting nodes instead? We don't want to parse the statement 
> everytime a variable binding comes in.

Sure. Sorry I wasn't being very specific. Also, whoever implements it
gets to do it either way at first :)

btw, I'm buried in trying to get a CASE statement to work, so am not
volunteering for this one...

                     - Tom