Re: plpgsql FOUND bug when SELECT INTO assigns a NULL - Mailing list pgsql-general

From Karl O. Pinc
Subject Re: plpgsql FOUND bug when SELECT INTO assigns a NULL
Date
Msg-id 1161335451l.20924l.14l@mofo
Whole thread Raw
In response to Re: plpgsql FOUND bug when SELECT INTO assigns a NULL value?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 10/19/2006 10:13:46 PM, Tom Lane wrote:
> "Karl O. Pinc" <kop@meme.com> writes:
> > I would expect that because a row exists, even
> > though the value assigned is NULL, FOUND would
> > be TRUE.  Are my expectations wrong?
>
> No, but I think your code is.  Please provide a test case
> demonstrating
> this behavior.

Thanks for the reply.  I suspect you're right.

After lots of investigation what seems to be happening
is that I'm putting data in in the wrong order....

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein


pgsql-general by date:

Previous
From: "Harpreet Dhaliwal"
Date:
Subject: Re: Can't get ECPG to connect (was Re: Urgen help required)
Next
From: "Ilja Golshtein"
Date:
Subject: Performance: fsync vs. commit delay