Re: user defined type, plpgsql function and NULL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Bjoern A(dot) Zeeb" <bzeeb-lists(at)lists(dot)zabbadoz(dot)net>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: user defined type, plpgsql function and NULL
Date: 2005-09-13 04:58:55
Message-ID: 19185.1126587535@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

"Bjoern A. Zeeb" <bzeeb-lists(at)lists(dot)zabbadoz(dot)net> writes:
> Is this correct or is it just a "works like that this time but may
> change at any time in the future"?

The meaning of a NULL for a composite value isn't real well-defined
at the moment. I tend to agree that "fbt IS NULL" should yield true
in your example, but I think there are/were some implementation reasons
why it doesn't.

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Gnanavel S 2005-09-13 05:01:33 Re: Age in days
Previous Message Michael Fuhr 2005-09-13 04:53:07 Re: How do I convert an integet to a timestamp?