Re: ECPG - bug in EXEC SQL WHENEVER NOT FOUND? - Mailing list pgsql-general

From Bruce Momjian
Subject Re: ECPG - bug in EXEC SQL WHENEVER NOT FOUND?
Date
Msg-id 200403081756.i28HurJ25780@candle.pha.pa.us
Whole thread Raw
In response to Re: ECPG - bug in EXEC SQL WHENEVER NOT FOUND?  (Christian Rank <christian.rank@rz.uni-passau.de>)
List pgsql-general
Christian Rank wrote:
> > postgres@feivel:/home/postgres/pgsql/src/interfaces/ecpg$ ./a
> > [21964]: ECPGdebug: set to 1
> > [21964]: ECPGconnect: opening database mm on <DEFAULT> port <DEFAULT>
> > [21964]: ECPGexecute line 16: QUERY: select  n   from t    on connection mm
> > [21964]: ECPGexecute line 16: Correctly got 0 tuples with 1 fields
> > [21964]: raising sqlcode 100 in line 16, 'No data found in line 16.'.
> > no data found
> > [21964]: ecpg_finish: Connection mm closed.
> >
> > Looks okay, doesn't it?
>
> Sorry that I didn't mention: I have PostgreSQL 7.4.1 on Slackware 9.1.
>
> Today I tried with a 7.5devel snapshot of 16.02.2004. In this version,
> everything works as it should, so I assume that this bug is fixed in the
> meantime.

And 7.4.2 (unreleased) notes state the fix:

     * Added ecpg WHENEVER NOT_FOUND to     SELECT/INSERT/UPDATE/DELETE

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-general by date:

Previous
From: "Markus Wollny"
Date:
Subject: Character Encoding Confusion
Next
From: Kris Jurka
Date:
Subject: Re: Character Encoding Confusion