Re: BUG #1056: ecpg ignores WHENEVER NOT FOUND - Mailing list pgsql-bugs

From Michael Meskes
Subject Re: BUG #1056: ecpg ignores WHENEVER NOT FOUND
Date
Msg-id 20040121141113.GA6657@1
Whole thread Raw
In response to BUG #1056: ecpg ignores WHENEVER NOT FOUND  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
List pgsql-bugs
On Tue, Jan 20, 2004 at 04:44:30PM -0400, PostgreSQL Bugs List wrote:
> Description:        ecpg ignores WHENEVER NOT FOUND

> ...
> This problem occurs with both 7.4 and 7.4.1.  The problem does not occur at
> ...
> I have a statement in my program such as:
>
>  EXEC SQL WHENEVER NOT FOUND GOTO nextvalError;
>
> The C code generated by ecpg at 7.4 and 7.4.1 is missing the statement:
>
>  if (sqlca.sqlcode == ECPG_NOT_FOUND) goto nextvalError;

For future bug reports, please add a test case as I can only guess now
what you're seeing.

I have found a bug and committed the fix to CVS, but I cannot tell now
if it also fixes your problem.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

pgsql-bugs by date:

Previous
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1057: psql sometimes does not flush its output
Next
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1058: unexpected output when using timezone() and to_char()