RE: [HACKERS] A small problem with the new inet and cidr types
Taral <taral@mail.utexas.edu>
From: "Taral" <taral@mail.utexas.edu>
To: "Tom Lane" <tgl@sss.pgh.pa.us>, "D'Arcy J.M. Cain" <darcy@druid.net>
Cc: <pgsql-hackers@postgreSQL.org>
Date: 1998-11-02T18:31:23Z
Lists: pgsql-hackers
> My guess is that maybe this should not be fixed in the individual > datatypes at all; instead the generic function and operator code should > be modified so that if any input value is NULL, then NULL is returned as > the result without ever calling the datatype-specific code. AFAICT, the function code returns blank when the input is NULL, regardless of the function definition... this came up before when someone tried to extend the functions and found that func(NULL) called func, but disregarded the return value... Taral