Date: Sun, 15 Jun 2003 12:55:17 +0200
From: Michael Meskes <meskes@postgresql.org>
To: BTS <bts_postgresql@hotmail.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: PREPARE in ECPG
Message-ID: <20030615105517.GD8944@feivel.fam-meskes.de>
Mail-Followup-To: BTS <bts_postgresql@hotmail.com>,
	pgsql-interfaces@postgresql.org
References: <Sea1-DAV59pyJp6y86l00016719@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Sea1-DAV59pyJp6y86l00016719@hotmail.com>
User-Agent: Mutt/1.5.4i

On Fri, May 23, 2003 at 08:55:07AM +0200, BTS wrote:
> The documentation for PostgreSQL 7.3 explains about introducing the optimized PREPARE/EXECUTE statements, but we have discovered this is not implemented (yet) in ECPG (we are using release 7.3.2). See comments in "ecpg/preproc/preproc.y".
> ...
> - When will the optimized PREPARE/EXECUTE be implemented in ECPG?

As soon as we find a way to do it. I do not see a good way to pass
variables to the backend's prepare statement. We had a longer discussion
on this starting with the different syntax until I understood that you
cannot prepare a statement like:

select * from table where id=:id;

until you already know the value of the variable id, i.e. the backend
does not know a USING clause to specify the variables when executing the
command.

But then I may have missed something. It happened before. :-)

Michael
-- 
Michael Meskes
Email: Michael@Fam-Meskes.De
ICQ: 179140304, AIM: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!