| From: | Mike Rylander <mrylander(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle vararg polymorphic functions) |
| Date: | 2005-06-24 13:44:10 |
| Message-ID: | b918cf3d05062406446f1d44c@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On 6/24/05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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)?
>
[snip]
>
> > Please, if You think, so Oracle way is good, correct it.
>
> I'm still favoring non-strict but it deserves more than two votes.
> Anybody else have an opinion?
>
> regards, tom lane
>
My $0.02: I'd prefer the non-strict version.
--
Mike Rylander
mrylander(at)gmail(dot)com
GPLS -- PINES Development
Database Developer
http://open-ils.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2005-06-24 13:50:47 | Re: Server instrumentation patch |
| Previous Message | Andrew Dunstan | 2005-06-24 13:41:32 | Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2005-06-24 14:56:07 | Re: [PATCHES] Function's LEAST, GREATEST and DECODE |
| Previous Message | Andrew Dunstan | 2005-06-24 13:41:32 | Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle |