Re: plpgsql FOUND bug when SELECT INTO assigns a NULL value?

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

"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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2006-10-20 03:40:10 Re: Ubuntu Help
Previous Message Michael Fuhr 2006-10-20 02:53:55 Re: PostGIS