Re: comparing null value in plpgsql. - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: comparing null value in plpgsql.
Date
Msg-id 20020310220729.O38817-100000@megazone23.bigpanda.com
Whole thread Raw
In response to comparing null value in plpgsql.  (Bhuvan A <bhuvansql@yahoo.com>)
Responses Re: comparing null value in plpgsql.
List pgsql-bugs
On Mon, 11 Mar 2002, Bhuvan A wrote:

> here i have a problem in comparing null values in plpgsql. this exist
> in 7.1.x and 7.2 as well.
>
> the condition <null value> != <valid value> fails in plpgsql.
> consider this function is triggered on every updation on a table.
>
>   create function ftest()
>   returns opaque as 'declare
>
>   begin
>
>     if new.comp_code != old.comp_code then
>       ...
>     end if;
>     return new;
>   end;'
>   language 'plpgsql';
>
> this condition fails if old.comp_code is null and new.comp_code has
> some value.

<nullvalue> != <anything> is not true, it's unknown, so the if shouldn't
fire.  It's a side effect of how the spec defines operations on nulls.

pgsql-bugs by date:

Previous
From: Bhuvan A
Date:
Subject: comparing null value in plpgsql.
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #611: configure script produces incorrect results under IRIX