AW: Re: [INTERFACES] USE OF CURSORS IN ECPG

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Christof Petig'" <christof(dot)petig(at)wtal(dot)de>, Maurizio <maurizio(dot)c(at)libero(dot)it>, Michael Meskes <meskes(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: Re: [INTERFACES] USE OF CURSORS IN ECPG
Date: 2000-11-10 12:10:19
Message-ID: 11C1E6749A55D411A9670001FA687963368106@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> PS: You might consider applying the patch for (update where > not_found) -> 100

No, this is not allowed. sqlcode is supposed to be 0 in above case.
You need to explicitly check for the number of rows updated in your
program if needed.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christof Petig 2000-11-10 12:49:33 Re: AW: Re: [INTERFACES] USE OF CURSORS IN ECPG
Previous Message Dirk Lutzebaeck 2000-11-10 11:19:21 Must a C state transition function use palloc on the returned value?