Re: ECPG: WHENEVER statement with DO CONTINUE action

Lists: pgsql-hackers
From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: meskes(at)postgresql(dot)org
Subject: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-06-09 08:01:36
Message-ID: 148022ca-3318-bbf2-d44e-37aac58658b6@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hello,

To develop the ECPG application more efficiently and improve portability,
I would like to suggest one minor improvement "WHENEVER condition *DO
CONTINUE*" support in ECPG.
Oracle Pro*C supports WHENEVER statement with DO CONTINUE action.[1]

EXEC SQL WHENEVER SQLERROR CONTINUE;
is not same as
EXEC SQL WHENEVER SQLERROR DO CONTINUE;

The CONTINUE action instructs the client application to proceed to the
next statement whereas DO CONTINUE action instructs the client
application to emit a C continue statement and the flow of control
return to the beginning of the enclosing loop.

I have tried to implement it. Please check the attached patch.

Please give me feedback.

[1]https://docs.oracle.com/cd/B28359_01/appdev.111/b28427/pc_09err.htm#i12340

Regards,

Vinayak Pokale
NTT Open Source Software Center

Attachment Content-Type Size
whenever-do-continue.patch binary/octet-stream 2.2 KB

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-06-09 08:38:50
Message-ID: 1496997530.2092.53.camel@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi,

> To develop the ECPG application more efficiently and improve
> portability,
> I would like to suggest one minor improvement "WHENEVER condition DO
> CONTINUE" support in ECPG.
> Oracle Pro*C supports WHENEVER statement with DO CONTINUE action.[1]
>
> EXEC SQL WHENEVER SQLERROR CONTINUE;
> is not same as
> EXEC SQL WHENEVER SQLERROR DO CONTINUE;
>
> The CONTINUE action instructs the client application to proceed to
> the next statement whereas DO CONTINUE action instructs the client
> application to emit a C continue statement and the flow of control
> return to the beginning of the enclosing loop.

This did actual escape me. Thanks for bringing it to our attention and
fixing this missing functionality.

> I have tried to implement it. Please check the attached patch.
> Please give me feedback.
> ...

Could you please add a "DO CONTINUE" case to one of the test cases? Or
add a new one? We would need a test case IMO.

Thanks

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! SF 49ers! Use Debian GNU/Linux, PostgreSQL


From: Vinayak Pokale <vinpokale(at)gmail(dot)com>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-06-10 03:23:33
Message-ID: CAEySZvgDHTMVhcs9hUNz9UBgR32a_mSC3aK0eZ8yOW2uSnQfGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Thank you for your reply

On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org> wrote:
>
> Hi,
>
> > To develop the ECPG application more efficiently and improve
> > portability,
> > I would like to suggest one minor improvement "WHENEVER condition DO
> > CONTINUE" support in ECPG.
> > Oracle Pro*C supports WHENEVER statement with DO CONTINUE action.[1]
> >
> > EXEC SQL WHENEVER SQLERROR CONTINUE;
> > is not same as
> > EXEC SQL WHENEVER SQLERROR DO CONTINUE;
> >
> > The CONTINUE action instructs the client application to proceed to
> > the next statement whereas DO CONTINUE action instructs the client
> > application to emit a C continue statement and the flow of control
> > return to the beginning of the enclosing loop.
>
> This did actual escape me. Thanks for bringing it to our attention and
> fixing this missing functionality.
>
> > I have tried to implement it. Please check the attached patch.
> > Please give me feedback.
> > ...
>
> Could you please add a "DO CONTINUE" case to one of the test cases? Or
> add a new one? We would need a test case IMO.
>
Yes I will add test case and send updated patch.

Regards,
Vinayak Pokale


From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-06-12 04:09:39
Message-ID: cc8573be-6e6d-94c9-70e0-b68ba8e81127@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi,

On 2017/06/10 12:23, Vinayak Pokale wrote:
>
> Thank you for your reply
>
> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org
> <mailto:meskes(at)postgresql(dot)org>> wrote:
> >
> > Could you please add a "DO CONTINUE" case to one of the test cases? Or
> > add a new one? We would need a test case IMO.
> >
> Yes I will add test case and send updated patch.
>
I have added new test case for DO CONTINUE.
Please check the attached patch.

Regards,
Vinayak Pokale
NTT Open Source Software Center

Attachment Content-Type Size
WHENEVER-statement-DO-CONTINUE-support.patch binary/octet-stream 17.7 KB

From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-06-20 04:51:25
Message-ID: ce446c52-62bc-4119-ca2d-6c1020c1b447@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2017/06/12 13:09, vinayak wrote:
>
> Hi,
>
> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>
>> Thank you for your reply
>>
>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org
>> <mailto:meskes(at)postgresql(dot)org>> wrote:
>> >
>> > Could you please add a "DO CONTINUE" case to one of the test cases? Or
>> > add a new one? We would need a test case IMO.
>> >
>> Yes I will add test case and send updated patch.
>>
> I have added new test case for DO CONTINUE.
> Please check the attached patch.
>
I have added this in Sept. CF
https://commitfest.postgresql.org/14/1173/

Regards,
Vinayak Pokale
NTT Open Source Software Center


From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-06-20 08:22:38
Message-ID: CAD21AoB3D26==n0zzj-H3p4PF8R7AxV_7w0dC1UW3yX1TFjTNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Jun 20, 2017 at 1:51 PM, vinayak
<Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>
>
> On 2017/06/12 13:09, vinayak wrote:
>
> Hi,
>
> On 2017/06/10 12:23, Vinayak Pokale wrote:
>
> Thank you for your reply
>
> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org> wrote:
>>
>> Could you please add a "DO CONTINUE" case to one of the test cases? Or
>> add a new one? We would need a test case IMO.
>>
> Yes I will add test case and send updated patch.
>
> I have added new test case for DO CONTINUE.
> Please check the attached patch.
>
> I have added this in Sept. CF
> https://commitfest.postgresql.org/14/1173/
>

I got the following warning by git show --check. I think you should
remove unnecessary whitespace. Also the code indent of
whenever_do_continue.pgc seems to need to be adjusted.

$ git show --check
commit a854aa0130589b7bd43b2c6c1c86651be91b1f59
Author: Vinayak Pokale <vinpokale(at)gmail(dot)com>
Date: Mon Jun 12 13:03:21 2017 +0900

WHENEVER statement DO CONTINUE support

src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:16: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:21: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:24: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:27: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:35: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:37: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:39: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:41: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:47: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:49: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:52: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:54: trailing
whitespace.
+
src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:1: new blank
line at EOF.

------
In whenever_do_continue.pgc file, the following line seems not to be
processed successfully by ecpg but should we fix that?

+
+ exec sql whenever sqlerror continue;
+

Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
action but that seems not to emit sqlerror, so "DO CONTINUE" is not
executed. I think the test case for DO CONTINUE should be a C code
that executes the "continue" clause.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-06-20 08:35:16
Message-ID: f6217873-734f-593d-1a15-429a029f219d@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi Sawada-san,

On 2017/06/20 17:22, Masahiko Sawada wrote:
> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>
>> On 2017/06/12 13:09, vinayak wrote:
>>
>> Hi,
>>
>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>
>> Thank you for your reply
>>
>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org> wrote:
>>> Could you please add a "DO CONTINUE" case to one of the test cases? Or
>>> add a new one? We would need a test case IMO.
>>>
>> Yes I will add test case and send updated patch.
>>
>> I have added new test case for DO CONTINUE.
>> Please check the attached patch.
>>
>> I have added this in Sept. CF
>> https://commitfest.postgresql.org/14/1173/
>>
> I got the following warning by git show --check. I think you should
> remove unnecessary whitespace. Also the code indent of
> whenever_do_continue.pgc seems to need to be adjusted.
>
> $ git show --check
> commit a854aa0130589b7bd43b2c6c1c86651be91b1f59
> Author: Vinayak Pokale <vinpokale(at)gmail(dot)com>
> Date: Mon Jun 12 13:03:21 2017 +0900
>
> WHENEVER statement DO CONTINUE support
>
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:16: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:21: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:24: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:27: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:35: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:37: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:39: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:41: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:47: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:49: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:52: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:54: trailing
> whitespace.
> +
> src/interfaces/ecpg/test/preproc/whenever_do_continue.pgc:1: new blank
> line at EOF.
>
> ------
> In whenever_do_continue.pgc file, the following line seems not to be
> processed successfully by ecpg but should we fix that?
>
> +
> + exec sql whenever sqlerror continue;
> +
>
> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
> executed. I think the test case for DO CONTINUE should be a C code
> that executes the "continue" clause.
Thank you for testing the patch.
I agreed with your comments. I will update the patch.

Regards,
Vinayak Pokale
NTT Open Source Software Center


From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-18 08:20:18
Message-ID: b82438fb-e085-f7d0-adc0-2583b6457400@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2017/06/20 17:35, vinayak wrote:
> Hi Sawada-san,
>
> On 2017/06/20 17:22, Masahiko Sawada wrote:
>> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>
>>> On 2017/06/12 13:09, vinayak wrote:
>>>
>>> Hi,
>>>
>>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>>
>>> Thank you for your reply
>>>
>>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org> wrote:
>>>> Could you please add a "DO CONTINUE" case to one of the test cases? Or
>>>> add a new one? We would need a test case IMO.
>>>>
>>> Yes I will add test case and send updated patch.
>>>
>>> I have added new test case for DO CONTINUE.
>>> Please check the attached patch.
>>>
>>> I have added this in Sept. CF
>>> https://commitfest.postgresql.org/14/1173/
>>>
>> ------
>> In whenever_do_continue.pgc file, the following line seems not to be
>> processed successfully by ecpg but should we fix that?
>>
>> +
>> + exec sql whenever sqlerror continue;
>> +
>>
>> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
>> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
>> executed. I think the test case for DO CONTINUE should be a C code
>> that executes the "continue" clause.
> Thank you for testing the patch.
> I agreed with your comments. I will update the patch.
Please check the attached updated patch.

Regards,
Vinayak Pokale
NTT Open Source Software Center

Attachment Content-Type Size
WHENEVER-statement-DO-CONTINUE-support_v1.patch text/x-diff 17.7 KB

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 02:07:33
Message-ID: CAD21AoDDCgac9Pbhc=G7_RW9KtLgP7Vk9kWStSEiv4Af8ZPh9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Aug 18, 2017 at 5:20 PM, vinayak
<Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>
> On 2017/06/20 17:35, vinayak wrote:
>>
>> Hi Sawada-san,
>>
>> On 2017/06/20 17:22, Masahiko Sawada wrote:
>>>
>>> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>
>>>>
>>>> On 2017/06/12 13:09, vinayak wrote:
>>>>
>>>> Hi,
>>>>
>>>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>>>
>>>> Thank you for your reply
>>>>
>>>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org> wrote:
>>>>>
>>>>> Could you please add a "DO CONTINUE" case to one of the test cases? Or
>>>>> add a new one? We would need a test case IMO.
>>>>>
>>>> Yes I will add test case and send updated patch.
>>>>
>>>> I have added new test case for DO CONTINUE.
>>>> Please check the attached patch.
>>>>
>>>> I have added this in Sept. CF
>>>> https://commitfest.postgresql.org/14/1173/
>>>>
>>> ------
>>> In whenever_do_continue.pgc file, the following line seems not to be
>>> processed successfully by ecpg but should we fix that?
>>>
>>> +
>>> + exec sql whenever sqlerror continue;
>>> +
>>>
>>> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
>>> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
>>> executed. I think the test case for DO CONTINUE should be a C code
>>> that executes the "continue" clause.
>>
>> Thank you for testing the patch.
>> I agreed with your comments. I will update the patch.
>
> Please check the attached updated patch.
>

Thank you for updating.

The regression test failed after applied latest patch by git am.

*** /tmp/pg/src/interfaces/ecpg/test/expected/preproc-whenever_do_continue.c
2017-08-24 20:01:10.023201132 -0700
--- /tmp/pg/src/interfaces/ecpg/test/results/preproc-whenever_do_continue.c
2017-08-24 20:22:54.308200853 -0700
***************
*** 140,147 ****
printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
}

! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the program to
! proceed if any further errors do occur. */
/* exec sql whenever sqlerror continue ; */
#line 53 "whenever_do_continue.pgc"

--- 140,147 ----
printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
}

! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the program to
! proceed if any further errors do occur. */
/* exec sql whenever sqlerror continue ; */
#line 53 "whenever_do_continue.pgc"

======================================================================

+ /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the program to
+ proceed if any further errors do occur. */

I think this comment should obey the coding style guide.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 05:57:59
Message-ID: d0933d18-6ab2-5b17-b217-55f5c27fbca5@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi Sawada-san,

On 2017/08/25 11:07, Masahiko Sawada wrote:
> On Fri, Aug 18, 2017 at 5:20 PM, vinayak
> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> On 2017/06/20 17:35, vinayak wrote:
>>> Hi Sawada-san,
>>>
>>> On 2017/06/20 17:22, Masahiko Sawada wrote:
>>>> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
>>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>>
>>>>> On 2017/06/12 13:09, vinayak wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>>>>
>>>>> Thank you for your reply
>>>>>
>>>>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org> wrote:
>>>>>> Could you please add a "DO CONTINUE" case to one of the test cases? Or
>>>>>> add a new one? We would need a test case IMO.
>>>>>>
>>>>> Yes I will add test case and send updated patch.
>>>>>
>>>>> I have added new test case for DO CONTINUE.
>>>>> Please check the attached patch.
>>>>>
>>>>> I have added this in Sept. CF
>>>>> https://commitfest.postgresql.org/14/1173/
>>>>>
>>>> ------
>>>> In whenever_do_continue.pgc file, the following line seems not to be
>>>> processed successfully by ecpg but should we fix that?
>>>>
>>>> +
>>>> + exec sql whenever sqlerror continue;
>>>> +
>>>>
>>>> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
>>>> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
>>>> executed. I think the test case for DO CONTINUE should be a C code
>>>> that executes the "continue" clause.
>>> Thank you for testing the patch.
>>> I agreed with your comments. I will update the patch.
>> Please check the attached updated patch.
>>
> Thank you for updating.
>
> The regression test failed after applied latest patch by git am.
>
> *** /tmp/pg/src/interfaces/ecpg/test/expected/preproc-whenever_do_continue.c
> 2017-08-24 20:01:10.023201132 -0700
> --- /tmp/pg/src/interfaces/ecpg/test/results/preproc-whenever_do_continue.c
> 2017-08-24 20:22:54.308200853 -0700
> ***************
> *** 140,147 ****
> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
> }
>
> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the program to
> ! proceed if any further errors do occur. */
> /* exec sql whenever sqlerror continue ; */
> #line 53 "whenever_do_continue.pgc"
>
> --- 140,147 ----
> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
> }
>
> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the program to
> ! proceed if any further errors do occur. */
> /* exec sql whenever sqlerror continue ; */
> #line 53 "whenever_do_continue.pgc"
>
> ======================================================================
>
> + /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the program to
> + proceed if any further errors do occur. */
>
> I think this comment should obey the coding style guide.
Thank you for testing.

I have updated the patch.
PFA.

Regards,
Vinayak Pokale
NTT Open Source Software Center

Attachment Content-Type Size
WHENEVER-statement-DO-CONTINUE-support_v2.patch text/x-patch 17.7 KB

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 07:18:22
Message-ID: CAD21AoBk+uCNzb7EzoFc9i6O26qxkYRT5U+wq-Cw6nQNWXgwQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Aug 25, 2017 at 2:57 PM, vinayak
<Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Hi Sawada-san,
>
>
> On 2017/08/25 11:07, Masahiko Sawada wrote:
>>
>> On Fri, Aug 18, 2017 at 5:20 PM, vinayak
>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>
>>> On 2017/06/20 17:35, vinayak wrote:
>>>>
>>>> Hi Sawada-san,
>>>>
>>>> On 2017/06/20 17:22, Masahiko Sawada wrote:
>>>>>
>>>>> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
>>>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>>>
>>>>>>
>>>>>> On 2017/06/12 13:09, vinayak wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>>>>>
>>>>>> Thank you for your reply
>>>>>>
>>>>>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org>
>>>>>> wrote:
>>>>>>>
>>>>>>> Could you please add a "DO CONTINUE" case to one of the test cases?
>>>>>>> Or
>>>>>>> add a new one? We would need a test case IMO.
>>>>>>>
>>>>>> Yes I will add test case and send updated patch.
>>>>>>
>>>>>> I have added new test case for DO CONTINUE.
>>>>>> Please check the attached patch.
>>>>>>
>>>>>> I have added this in Sept. CF
>>>>>> https://commitfest.postgresql.org/14/1173/
>>>>>>
>>>>> ------
>>>>> In whenever_do_continue.pgc file, the following line seems not to be
>>>>> processed successfully by ecpg but should we fix that?
>>>>>
>>>>> +
>>>>> + exec sql whenever sqlerror continue;
>>>>> +
>>>>>
>>>>> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
>>>>> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
>>>>> executed. I think the test case for DO CONTINUE should be a C code
>>>>> that executes the "continue" clause.
>>>>
>>>> Thank you for testing the patch.
>>>> I agreed with your comments. I will update the patch.
>>>
>>> Please check the attached updated patch.
>>>
>> Thank you for updating.
>>
>> The regression test failed after applied latest patch by git am.
>>
>> ***
>> /tmp/pg/src/interfaces/ecpg/test/expected/preproc-whenever_do_continue.c
>> 2017-08-24 20:01:10.023201132 -0700
>> ---
>> /tmp/pg/src/interfaces/ecpg/test/results/preproc-whenever_do_continue.c
>> 2017-08-24 20:22:54.308200853 -0700
>> ***************
>> *** 140,147 ****
>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
>> }
>>
>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>> program to
>> ! proceed if any further errors do occur. */
>> /* exec sql whenever sqlerror continue ; */
>> #line 53 "whenever_do_continue.pgc"
>>
>> --- 140,147 ----
>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
>> }
>>
>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>> program to
>> ! proceed if any further errors do occur. */
>> /* exec sql whenever sqlerror continue ; */
>> #line 53 "whenever_do_continue.pgc"
>>
>> ======================================================================
>>
>> + /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>> program to
>> + proceed if any further errors do occur. */
>>
>> I think this comment should obey the coding style guide.
>
> Thank you for testing.
>
> I have updated the patch.
> PFA.
>

Thank you for updating the patch. It seems not to incorporate my
second review comment. Attached an updated patch including a fix of a
comment style in whenever_do_continue.pgc file. Please find an
attached file.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment Content-Type Size
0001-WHENEVER-statement-DO-CONTINUE-support_v3.patch application/octet-stream 17.7 KB

From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 07:27:55
Message-ID: 0f221745-54dd-54f7-aceb-9244984b6dcc@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2017/08/25 16:18, Masahiko Sawada wrote:
> On Fri, Aug 25, 2017 at 2:57 PM, vinayak
> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> Hi Sawada-san,
>>
>>
>> On 2017/08/25 11:07, Masahiko Sawada wrote:
>>> On Fri, Aug 18, 2017 at 5:20 PM, vinayak
>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>> On 2017/06/20 17:35, vinayak wrote:
>>>>> Hi Sawada-san,
>>>>>
>>>>> On 2017/06/20 17:22, Masahiko Sawada wrote:
>>>>>> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
>>>>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>>>>
>>>>>>> On 2017/06/12 13:09, vinayak wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>>>>>>
>>>>>>> Thank you for your reply
>>>>>>>
>>>>>>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org>
>>>>>>> wrote:
>>>>>>>> Could you please add a "DO CONTINUE" case to one of the test cases?
>>>>>>>> Or
>>>>>>>> add a new one? We would need a test case IMO.
>>>>>>>>
>>>>>>> Yes I will add test case and send updated patch.
>>>>>>>
>>>>>>> I have added new test case for DO CONTINUE.
>>>>>>> Please check the attached patch.
>>>>>>>
>>>>>>> I have added this in Sept. CF
>>>>>>> https://commitfest.postgresql.org/14/1173/
>>>>>>>
>>>>>> ------
>>>>>> In whenever_do_continue.pgc file, the following line seems not to be
>>>>>> processed successfully by ecpg but should we fix that?
>>>>>>
>>>>>> +
>>>>>> + exec sql whenever sqlerror continue;
>>>>>> +
>>>>>>
>>>>>> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
>>>>>> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
>>>>>> executed. I think the test case for DO CONTINUE should be a C code
>>>>>> that executes the "continue" clause.
>>>>> Thank you for testing the patch.
>>>>> I agreed with your comments. I will update the patch.
>>>> Please check the attached updated patch.
>>>>
>>> Thank you for updating.
>>>
>>> The regression test failed after applied latest patch by git am.
>>>
>>> ***
>>> /tmp/pg/src/interfaces/ecpg/test/expected/preproc-whenever_do_continue.c
>>> 2017-08-24 20:01:10.023201132 -0700
>>> ---
>>> /tmp/pg/src/interfaces/ecpg/test/results/preproc-whenever_do_continue.c
>>> 2017-08-24 20:22:54.308200853 -0700
>>> ***************
>>> *** 140,147 ****
>>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
>>> }
>>>
>>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>> program to
>>> ! proceed if any further errors do occur. */
>>> /* exec sql whenever sqlerror continue ; */
>>> #line 53 "whenever_do_continue.pgc"
>>>
>>> --- 140,147 ----
>>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal, emp.comm);
>>> }
>>>
>>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>> program to
>>> ! proceed if any further errors do occur. */
>>> /* exec sql whenever sqlerror continue ; */
>>> #line 53 "whenever_do_continue.pgc"
>>>
>>> ======================================================================
>>>
>>> + /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>> program to
>>> + proceed if any further errors do occur. */
>>>
>>> I think this comment should obey the coding style guide.
>> Thank you for testing.
>>
>> I have updated the patch.
>> PFA.
>>
> Thank you for updating the patch. It seems not to incorporate my
> second review comment. Attached an updated patch including a fix of a
> comment style in whenever_do_continue.pgc file. Please find an
> attached file.
Sorry, I missed it.
Thank you for fixing the comment style.

Regards,
Vinayak Pokale
NTT Open Source Software Center


From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 08:13:16
Message-ID: CAD21AoDDiNiMBn_CDQsD5MiOd9CunWvxyuzrJJQCanTyUk-Wzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Aug 25, 2017 at 4:27 PM, vinayak
<Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>
>
> On 2017/08/25 16:18, Masahiko Sawada wrote:
>>
>> On Fri, Aug 25, 2017 at 2:57 PM, vinayak
>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>
>>> Hi Sawada-san,
>>>
>>>
>>> On 2017/08/25 11:07, Masahiko Sawada wrote:
>>>>
>>>> On Fri, Aug 18, 2017 at 5:20 PM, vinayak
>>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>>
>>>>> On 2017/06/20 17:35, vinayak wrote:
>>>>>>
>>>>>> Hi Sawada-san,
>>>>>>
>>>>>> On 2017/06/20 17:22, Masahiko Sawada wrote:
>>>>>>>
>>>>>>> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
>>>>>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On 2017/06/12 13:09, vinayak wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>>>>>>>
>>>>>>>> Thank you for your reply
>>>>>>>>
>>>>>>>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Could you please add a "DO CONTINUE" case to one of the test cases?
>>>>>>>>> Or
>>>>>>>>> add a new one? We would need a test case IMO.
>>>>>>>>>
>>>>>>>> Yes I will add test case and send updated patch.
>>>>>>>>
>>>>>>>> I have added new test case for DO CONTINUE.
>>>>>>>> Please check the attached patch.
>>>>>>>>
>>>>>>>> I have added this in Sept. CF
>>>>>>>> https://commitfest.postgresql.org/14/1173/
>>>>>>>>
>>>>>>> ------
>>>>>>> In whenever_do_continue.pgc file, the following line seems not to be
>>>>>>> processed successfully by ecpg but should we fix that?
>>>>>>>
>>>>>>> +
>>>>>>> + exec sql whenever sqlerror continue;
>>>>>>> +
>>>>>>>
>>>>>>> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
>>>>>>> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
>>>>>>> executed. I think the test case for DO CONTINUE should be a C code
>>>>>>> that executes the "continue" clause.
>>>>>>
>>>>>> Thank you for testing the patch.
>>>>>> I agreed with your comments. I will update the patch.
>>>>>
>>>>> Please check the attached updated patch.
>>>>>
>>>> Thank you for updating.
>>>>
>>>> The regression test failed after applied latest patch by git am.
>>>>
>>>> ***
>>>> /tmp/pg/src/interfaces/ecpg/test/expected/preproc-whenever_do_continue.c
>>>> 2017-08-24 20:01:10.023201132 -0700
>>>> ---
>>>> /tmp/pg/src/interfaces/ecpg/test/results/preproc-whenever_do_continue.c
>>>> 2017-08-24 20:22:54.308200853 -0700
>>>> ***************
>>>> *** 140,147 ****
>>>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal,
>>>> emp.comm);
>>>> }
>>>>
>>>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>>> program to
>>>> ! proceed if any further errors do occur. */
>>>> /* exec sql whenever sqlerror continue ; */
>>>> #line 53 "whenever_do_continue.pgc"
>>>>
>>>> --- 140,147 ----
>>>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal,
>>>> emp.comm);
>>>> }
>>>>
>>>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>>> program to
>>>> ! proceed if any further errors do occur. */
>>>> /* exec sql whenever sqlerror continue ; */
>>>> #line 53 "whenever_do_continue.pgc"
>>>>
>>>> ======================================================================
>>>>
>>>> + /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>>> program to
>>>> + proceed if any further errors do occur. */
>>>>
>>>> I think this comment should obey the coding style guide.
>>>
>>> Thank you for testing.
>>>
>>> I have updated the patch.
>>> PFA.
>>>
>> Thank you for updating the patch. It seems not to incorporate my
>> second review comment. Attached an updated patch including a fix of a
>> comment style in whenever_do_continue.pgc file. Please find an
>> attached file.
>
> Sorry, I missed it.
> Thank you for fixing the comment style.
>

The v3 patch looks good to me. I've changed this patch status to Ready
for Committer.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 08:20:24
Message-ID: 453b9734-a70c-0ad0-5966-2fd94f829781@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2017/08/25 17:13, Masahiko Sawada wrote:
> On Fri, Aug 25, 2017 at 4:27 PM, vinayak
> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>
>> On 2017/08/25 16:18, Masahiko Sawada wrote:
>>> On Fri, Aug 25, 2017 at 2:57 PM, vinayak
>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>> Hi Sawada-san,
>>>>
>>>>
>>>> On 2017/08/25 11:07, Masahiko Sawada wrote:
>>>>> On Fri, Aug 18, 2017 at 5:20 PM, vinayak
>>>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>>> On 2017/06/20 17:35, vinayak wrote:
>>>>>>> Hi Sawada-san,
>>>>>>>
>>>>>>> On 2017/06/20 17:22, Masahiko Sawada wrote:
>>>>>>>> On Tue, Jun 20, 2017 at 1:51 PM, vinayak
>>>>>>>> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>>>>>>>>
>>>>>>>>> On 2017/06/12 13:09, vinayak wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> On 2017/06/10 12:23, Vinayak Pokale wrote:
>>>>>>>>>
>>>>>>>>> Thank you for your reply
>>>>>>>>>
>>>>>>>>> On Jun 9, 2017 5:39 PM, "Michael Meskes" <meskes(at)postgresql(dot)org>
>>>>>>>>> wrote:
>>>>>>>>>> Could you please add a "DO CONTINUE" case to one of the test cases?
>>>>>>>>>> Or
>>>>>>>>>> add a new one? We would need a test case IMO.
>>>>>>>>>>
>>>>>>>>> Yes I will add test case and send updated patch.
>>>>>>>>>
>>>>>>>>> I have added new test case for DO CONTINUE.
>>>>>>>>> Please check the attached patch.
>>>>>>>>>
>>>>>>>>> I have added this in Sept. CF
>>>>>>>>> https://commitfest.postgresql.org/14/1173/
>>>>>>>>>
>>>>>>>> ------
>>>>>>>> In whenever_do_continue.pgc file, the following line seems not to be
>>>>>>>> processed successfully by ecpg but should we fix that?
>>>>>>>>
>>>>>>>> +
>>>>>>>> + exec sql whenever sqlerror continue;
>>>>>>>> +
>>>>>>>>
>>>>>>>> Also, you wrote the test case using "WHENEVER sqlerror DO CONTINUE"
>>>>>>>> action but that seems not to emit sqlerror, so "DO CONTINUE" is not
>>>>>>>> executed. I think the test case for DO CONTINUE should be a C code
>>>>>>>> that executes the "continue" clause.
>>>>>>> Thank you for testing the patch.
>>>>>>> I agreed with your comments. I will update the patch.
>>>>>> Please check the attached updated patch.
>>>>>>
>>>>> Thank you for updating.
>>>>>
>>>>> The regression test failed after applied latest patch by git am.
>>>>>
>>>>> ***
>>>>> /tmp/pg/src/interfaces/ecpg/test/expected/preproc-whenever_do_continue.c
>>>>> 2017-08-24 20:01:10.023201132 -0700
>>>>> ---
>>>>> /tmp/pg/src/interfaces/ecpg/test/results/preproc-whenever_do_continue.c
>>>>> 2017-08-24 20:22:54.308200853 -0700
>>>>> ***************
>>>>> *** 140,147 ****
>>>>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal,
>>>>> emp.comm);
>>>>> }
>>>>>
>>>>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>>>> program to
>>>>> ! proceed if any further errors do occur. */
>>>>> /* exec sql whenever sqlerror continue ; */
>>>>> #line 53 "whenever_do_continue.pgc"
>>>>>
>>>>> --- 140,147 ----
>>>>> printf("%s %7.2f %9.2f\n", emp.ename, emp.sal,
>>>>> emp.comm);
>>>>> }
>>>>>
>>>>> ! /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>>>> program to
>>>>> ! proceed if any further errors do occur. */
>>>>> /* exec sql whenever sqlerror continue ; */
>>>>> #line 53 "whenever_do_continue.pgc"
>>>>>
>>>>> ======================================================================
>>>>>
>>>>> + /* This 'CONTINUE' shuts off the 'DO CONTINUE' and allow the
>>>>> program to
>>>>> + proceed if any further errors do occur. */
>>>>>
>>>>> I think this comment should obey the coding style guide.
>>>> Thank you for testing.
>>>>
>>>> I have updated the patch.
>>>> PFA.
>>>>
>>> Thank you for updating the patch. It seems not to incorporate my
>>> second review comment. Attached an updated patch including a fix of a
>>> comment style in whenever_do_continue.pgc file. Please find an
>>> attached file.
>> Sorry, I missed it.
>> Thank you for fixing the comment style.
>>
> The v3 patch looks good to me. I've changed this patch status to Ready
> for Committer.
Thank you for updating the status in the CF.
We can wait for committers feedback.

Regards,
Vinayak Pokale
NTT Open Source Software Center


From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 13:45:06
Message-ID: 9f2e5118-b3fc-fc7d-aae1-e636478afbf5@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> The v3 patch looks good to me. I've changed this patch status to Ready
> for Committer.

Thank you all, committed.

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: Vinayak Pokale <vinpokale(at)gmail(dot)com>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 13:52:17
Message-ID: CAEySZvj-PXAsVqBwVMdpTRFkRN=4JNqB4VW3zr7adK4HpdboPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Aug 25, 2017 10:45 PM, "Michael Meskes" <meskes(at)postgresql(dot)org> wrote:
>
> > The v3 patch looks good to me. I've changed this patch status to Ready
> > for Committer.
>
> Thank you all, committed.

Thank you very much.

Regards,
Vinayak Pokale


From: Christian Ullrich <chris(at)chrullrich(dot)net>
To: Michael Meskes <meskes(at)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 14:05:55
Message-ID: 0975f4bb-5dee-c33c-b719-3ce44026d397@chrullrich.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

* Michael Meskes wrote:

>> The v3 patch looks good to me. I've changed this patch status to Ready
>> for Committer.
>
> Thank you all, committed.

The buildfarm says that sorting is frequently done case-sensitively:

*** 1,2 ****
- josh 10000.00 10.00
Ram 111100.00 21.00
--- 1,2 ----
Ram 111100.00 21.00
+ josh 10000.00 10.00

--
Christian


From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christian Ullrich <chris(at)chrullrich(dot)net>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-25 18:04:30
Message-ID: 10845.1503684270@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Christian Ullrich <chris(at)chrullrich(dot)net> writes:
> The buildfarm says that sorting is frequently done case-sensitively:

Given that it's Friday evening in Europe, I'm betting Michael is gone
for the day. In the interests of getting the buildfarm back to green,
I'll see if I can fix this.

regards, tom lane


From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christian Ullrich <chris(at)chrullrich(dot)net>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG: WHENEVER statement with DO CONTINUE action
Date: 2017-08-26 10:49:58
Message-ID: 1503744598.2125.192.camel@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> Given that it's Friday evening in Europe, I'm betting Michael is gone
> for the day.  In the interests of getting the buildfarm back to
> green,
> I'll see if I can fix this.

Correct, thanks Tom.

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! SF 49ers! Use Debian GNU/Linux, PostgreSQL