Thread

1. ECPG, cursors and transactions

   PostgreSQL Bugs List <pgsql-bugs@postgresql.org> — 2001-01-17T12:44:01Z

   Ing. Pavel Janousek (janousek@fonet.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 ...
   
   

2. Re: ECPG, cursors and transactions

   Christof Petig <christof@petig-baender.de> — 2001-01-30T21:13:54Z

   pgsql-bugs@postgresql.org wrote:
   
   > Ing. Pavel Janousek (janousek@fonet.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