From: | Christof Petig <christof(at)petig-baender(dot)de> |
---|---|
To: | janousek(at)fonet(dot)cz, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: ECPG, cursors and transactions |
Date: | 2001-01-30 21:13:54 |
Message-ID: | 3A772E92.EEE52EB6@petig-baender.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org wrote:
> Ing. Pavel Janousek (janousek(at)fonet(dot)cz) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> ECPG, cursors and transactions
>
> Long Description
> When I use ECPG in transactions I got some bad results - I think that this results are bug, but I'm not sure... (Pglib implementation?, ECPG implementation?)
>
> When I use ECPG like this:
> exec sql include sqlca;
> exec sql whenever sqlerror do sqlprint ();
> exec sql connect...
> exec sql declare cur cursor ....
> exec sql open cur;
> exec sql whenever not found do break;
> while (1)
> {
> exec sql fetch in cur into ...
if
exec sql set autocommit to off;
does not fix your problems then please give more details. (program output etc.) IMHO this should be the default - but unfortunately it isn't ...
Christof
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 2001-01-30 23:31:53 | Re: [JDBC] no way in LargeObject API to detect short read? |
Previous Message | Myron Scott | 2001-01-30 09:25:19 | PROC struct |