| From: | "Higuchi, Daisuke" <higuchi(dot)daisuke(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: [Bug Fix] ECPG: could not use set xxx to default statement |
| Date: | 2019-02-19 09:38:01 |
| Message-ID: | 1803D792815FC24D871C00D17AE95905DB551E@g01jpexmbkw24 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> I think we need to fix that script to either cope with missing semicolons,
> or at least complain about them. Too tired to look into how, right now.
I attached the patch which cope with missing semicolons.
Previous parse.pl find semicolon and dump data to buffer. When attached patch's parse.pl find new tokens before finding a semicolon, it also dumps data to buffer.
Regards,
Daisuke, Higuchi
| Attachment | Content-Type | Size |
|---|---|---|
| FIX_ECPG_SET_TO_DEFAULT_v2.patch | application/octet-stream | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-02-19 09:57:59 | Re: Prepared transaction releasing locks before deregistering its GID |
| Previous Message | Michael Meskes | 2019-02-19 09:26:51 | Re: [Bug Fix] ECPG: could not use set xxx to default statement |