Re: plpgsql FOUND bug when SELECT INTO assigns a NULL

From: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: plpgsql FOUND bug when SELECT INTO assigns a NULL
Date: 2006-10-20 09:10:51
Message-ID: 1161335451l.20924l.14l@mofo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 10/19/2006 10:13:46 PM, Tom Lane wrote:
> "Karl O. Pinc" <kop(at)meme(dot)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(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ilja Golshtein 2006-10-20 09:40:42 Performance: fsync vs. commit delay
Previous Message Harpreet Dhaliwal 2006-10-20 09:07:53 Re: Can't get ECPG to connect (was Re: Urgen help required)