[ moving to -hackers for a wider audience ]
Today's issue: should the GREATEST/LEAST functions be strict (return
null if any input is null) or not (return null only if all inputs are
null, else return the largest/smallest of the non-null inputs)?
Pavel Stehule [EMAIL PROTECTED] writes:
On Thu,
On 6/24/05, Tom Lane [EMAIL PROTECTED] wrote:
[ moving to -hackers for a wider audience ]
Today's issue: should the GREATEST/LEAST functions be strict (return
null if any input is null) or not (return null only if all inputs are
null, else return the largest/smallest of the non-null inputs)?
@postgresql.org
Subject: Re: [HACKERS] [PATCHES] Function's LEAST, GREATEST
and DECODE (Oracle vararg polymorphic functions)
[ moving to -hackers for a wider audience ]
Today's issue: should the GREATEST/LEAST functions be strict
(return null if any input is null) or not (return null only
John Hansen [EMAIL PROTECTED] writes:
I'd vote that these functions should follow the semantics of the , and
operators.
(NULL x) is NULL;
Well, that's a fair analogy, but then so is the analogy to MAX/MIN ...
so it seems about a wash to me.
regards, tom lane
On Fri, Jun 24, 2005 at 09:21:25AM -0400, Tom Lane wrote:
[ moving to -hackers for a wider audience ]
Today's issue: should the GREATEST/LEAST functions be strict (return
null if any input is null) or not (return null only if all inputs
are null, else return the largest/smallest of the