| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | "Ideriha, Takeshi" <ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DECLARE STATEMENT setting up a connection in ECPG |
| Date: | 2016-11-17 19:45:01 |
| Message-ID: | 20161117194501.svz7pc4ouoyeuxnn@feivel |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> [System Design Plan]
> To support above functionality, ecpg precompiler should support:
> - To understand the DECLARE STATEMENT syntax
Already does, albeit as a noop.
> - Translate the DECLARE STATEMENT into a new function with parameters.
> These parameters carry the information like connection_name and statement_name.
> - The function is a new function defined in the ECPG library.
Why's that? I haven't checked if the standard says anything about this and my
memory might be wrong, but isn't "DECLARE STATEMENT" supposed to be purely
declarative, i.e. not executed at run time?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-11-17 20:04:59 | Re: amcheck (B-Tree integrity checking tool) |
| Previous Message | Robert Haas | 2016-11-17 19:16:31 | Re: Fun fact about autovacuum and orphan temp tables |