| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
| Cc: | 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 polymorphic functions) |
| Date: | 2005-06-24 02:26:55 |
| Message-ID: | 21609.1119580015@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> writes:
+ /* If any argument is null, then result is null (for GREATEST and LEAST)*/
Are you sure about that? The only reference I could find says that
these functions are not strict in Oracle:
http://download-east.oracle.com/otn_hosted_doc/rdb/pdf/sql_ref_v71_vol1.pdf
on page 2-185:
The NULL keyword can appear in the list but is ignored. However, not all
value expressions can be specified as NULL. That is, a non-NULL value
expression must be in the list so that the data type for the expression
can be determined.
The GREATEST and LEAST functions can result in NULL only if at run time
all value expressions result in NULL.
The strict interpretation is mathematically cleaner, no doubt, but
offhand it seems less useful.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew - Supernews | 2005-06-24 02:26:57 | Re: pgsql: Fix rtree and contrib/rtree_gist search behavior for the 1-D box |
| Previous Message | Qingqing Zhou | 2005-06-24 02:14:22 | Re: regression failure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2005-06-24 02:43:41 | Re: EUC_JP and SJIS conversion improvement |
| Previous Message | Tom Lane | 2005-06-24 01:57:57 | Re: language handlers in public schema? |