Re: [HACKERS] A small problem with the new inet and cidr types - Mailing list pgsql-hackers

From darcy@druid.net (D'Arcy J.M. Cain)
Subject Re: [HACKERS] A small problem with the new inet and cidr types
Date
Msg-id m0zagtY-0000eRC@druid.net
Whole thread Raw
In response to Re: [HACKERS] A small problem with the new inet and cidr types  (Hannu Krosing <hannu@trust.ee>)
Responses Re: [HACKERS] A small problem with the new inet and cidr types  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Thus spake Hannu Krosing
> D'Arcy J.M. Cain wrote:
> > There may be cases where a function of a null is not null as some people
> > have pointed out but so far no one has come up with a practical example.
> 
> isnull(field)
> 
> is_any_null(field1,field2,field3)
> 
> are_all_nulls(field1,field2,field3)
> 
> value_or_default(NULL,defaultvalue)

I meant in the specific type functions.  These functions seem like they
can easily be handled at a higher level and still never call the type
function code.  IOW, if these functions are considered useful, they
should be implemented at the function dispatch level.

That last one seems particularly useful to me and, in fact, could handle
the issue of requiring functions to handle nulls all by itself.

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 424 2871     (DoD#0082)    (eNTP)   |  what's for dinner.


pgsql-hackers by date:

Previous
From: Jason
Date:
Subject: RE: [GENERAL] Upcoming 6.4 release issues
Next
From: darcy@druid.net (D'Arcy J.M. Cain)
Date:
Subject: Re: [HACKERS] A small problem with the new inet and cidr typesg