From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | BTS <bts_postgresql(at)hotmail(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: PREPARE in ECPG |
Date: | 2003-06-15 10:55:17 |
Message-ID: | 20030615105517.GD8944@feivel.fam-meskes.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(at)Fam-Meskes(dot)De
ICQ: 179140304, AIM: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2003-06-15 10:58:33 | Re: PREPARE in ECPG |
Previous Message | rino.79 | 2003-06-13 18:23:45 | Info |