Search Postgresql Archives

Re: plpgsql FOUND bug when SELECT INTO assigns a NULL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux