| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-patches(at)postgresql(dot)org, neilc(at)samurai(dot)com, david(at)fetter(dot)org |
| Subject: | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg |
| Date: | 2005-06-21 19:15:20 |
| Message-ID: | 15295.1119381320@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Oh, and I personally think DECODE is fine, even if it partly duplicates
> something we already have. I was just asking to make sure everyone else
> was OK before I applied it.
I would rather not have a useless variant spelling of CASE ...
LEAST/GREATEST at least do something that's a bit hard to do otherwise.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-06-21 19:56:13 | Strange logic for partial index proving |
| Previous Message | Bruce Momjian | 2005-06-21 19:10:03 | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-06-21 20:14:07 | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg |
| Previous Message | Marc G. Fournier | 2005-06-21 19:13:11 | Re: dbsize backend integration |