Re: BUG #1056: ecpg ignores WHENEVER NOT FOUND

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>
Cc: wespgc(at)syntegra(dot)com
Subject: Re: BUG #1056: ecpg ignores WHENEVER NOT FOUND
Date: 2004-01-21 14:11:13
Message-ID: 20040121141113.GA6657@1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-01-21 15:39:10 BUG #1058: unexpected output when using timezone() and to_char()
Previous Message bs 2004-01-21 09:51:13 7.4.xx regression