Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle
Date: 2005-06-24 13:41:32
Message-ID: 42BC0D8C.5070900@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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 non-null inputs)?
>
>
>

My initial reaction was to say "not strict", and since that's apparently
what Oracle does that reinforces it for me.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mike Rylander 2005-06-24 13:44:10 Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle vararg polymorphic functions)
Previous Message Tom Lane 2005-06-24 13:37:23 Re: [PATCHES] O_DIRECT for WAL writes

Browse pgsql-patches by date

  From Date Subject
Next Message Mike Rylander 2005-06-24 13:44:10 Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle vararg polymorphic functions)
Previous Message Tom Lane 2005-06-24 13:37:23 Re: [PATCHES] O_DIRECT for WAL writes