From: | "Ideriha, Takeshi" <ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
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-21 04:11:24 |
Message-ID: | 4E72940DA2BF16479384A86D54D0988A4D81D46E@G01JPEXMBKW04 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thank you for your comment.
Friday, November 18, 2016 4:45 AM Michael Meskes wrote :
> > - 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?
My lack of explanation caused the confusion, sorry.
Your point is true.
"DECLARE STATEMENT" is declarative ,not function in .pgc file.
I wanted to say that in order to use the connection pointed
by the DECLARE STATEMENT some functions like ECPGdo() would be modified or
new function would be added under the directory ecpglib/.
This modification or new function will be used to get the connection by statement_name.
Regards,
Ideriha, Takeshi
Fujitsu
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2016-11-21 04:23:49 | Re: Document how to set up TAP tests for Perl 5.8.8 |
Previous Message | Craig Ringer | 2016-11-21 04:08:04 | Re: pg_recvlogical --endpos |