Re: COALESCE and NULLIF semantics

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org, Sam Mason <sam(at)samason(dot)me(dot)uk>
Subject: Re: COALESCE and NULLIF semantics
Date: 2009-09-11 21:35:07
Message-ID: 11581.1252704907@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> To make that interpretation work I think you would need to say that
> ROW(NULL,NULL) _is_ the null value,

Right...

> and you would have to allow things like:

> select 1 + row(null,null);

Eh? It's a null value of a composite type. The above is a type
violation.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-09-11 21:45:07 Re: COPY enhancements
Previous Message Tom Lane 2009-09-11 21:32:42 Re: COPY enhancements