Tom,
Thanks for that. Coalesce worked like a ripper. It even forced me to update the database to 6.5.2. I'd been putting it
offfor a while.
Gary
>>> Tom Lane <tgl@sss.pgh.pa.us> 15/11/99 16:10:51 >>>
"Gary MacMinn" <G.MacMinn@nca.gov.au> writes:
> I'm trying to find out if PostgreSQL has a function like NVL that
> replaces null values with a default?
NVL is not in the SQL standard. But COALESCE is, and you can get
what you want withCOALESCE(x, value-to-use-if-x-is-null)
I'd recommend updating to 6.5.2 or later before doing much with
COALESCE --- it depends on CASE which was fairly buggy in older
releases.
> I have a table with datetime fields, some of which are null. I'm
> trying to extract the date and time components with the date() and
> time() functions but the null values break these functions.
Hmmm ...
regression=> SELECT t1, date(d1) from test1;
ERROR: Unable to convert null datetime to date
regression=> SELECT t1, time(d1) from test1;
ERROR: Unable to convert null datetime to date
This is undesirable, I agree. It seems to me that those routines should
just return NULL given NULL input, rather than going out of their way to
break applications. Thomas, can you defend this behavior?
regards, tom lane
************