| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | execute immediate |
| Date: | 2007-06-13 12:52:41 |
| Message-ID: | 20070613125241.GA27209@feivel.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
According to the standard EXEC SQL EXECUTE IMMEDIATE dynamically
prepares and executes a statement. ECPG used to just simulate this by
simply executing the statement. But before rewriting this I wonder if it
makes any sense at all. Where's the advantage of preparing a statement,
then executing it and then of course deallocating it again over a simple
execution?
The EXEC SQL EXECUTE IMMEDIATE clause is needed to be able to
dynamically compute the statement to be executed, but do we really need
to prepare it?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | René Grün | 2007-06-15 13:38:03 | NAN-Values in ECPG-Code |
| Previous Message | Michael Meskes | 2007-06-08 20:36:06 | Re: PQprepare case sensitive? |