Re: [GENERAL] plpgsql FOUND bug when SELECT INTO assigns a NULL

2006-10-20 Thread Karl O. Pinc
On 10/19/2006 10:13:46 PM, Tom Lane wrote: "Karl O. Pinc" <[EMAIL PROTECTED]> 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

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

2006-10-19 Thread Tom Lane
"Karl O. Pinc" <[EMAIL PROTECTED]> 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. regard

[GENERAL] plpgsql FOUND bug when SELECT INTO assigns a NULL value?

2006-10-19 Thread Karl O. Pinc
Hi, The docs say: A SELECT INTO statement sets FOUND true if it returns a row, false if no row is returned. I'm running a plpgsql procedure from a trigger and am doing a "SELECT INTO foo bar ..." where a row matches the selection criteria, but the value of that row's bar column is NULL. The