| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | Nicholas White <n(dot)j(dot)white(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Troels Nielsen <bn(dot)troels(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |
| Date: | 2013-07-01 06:58:17 |
| Message-ID: | CAEZATCX++qyALrAWhm9GA=BT3Zg-_gdJrYwmF2kFfmvFvt_MhA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 July 2013 03:07, Nicholas White <n(dot)j(dot)white(at)gmail(dot)com> wrote:
>> Alternatively, it might be trivial to make all aggregate functions work
>> with ignore nulls in a window context
>
> This is a good idea, but I'd like to keep the scope of this patch limited
> for the time being
Agreed.
> - I'll look at doing this (along with the first / last /
> nth value window functions) for a later release.
>
On the other hand, perhaps this is not worth doing for aggregates,
since in that case IGNORE NULLS is just a special case of FILTER
(WHERE ...). Making IGNORE NULLS work for the other window functions
is probably more useful, as you say, in a future patch.
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ian link | 2013-07-01 07:05:36 | Re: Support for RANGE ... PRECEDING windows in OVER |
| Previous Message | Hannu Krosing | 2013-07-01 06:36:56 | Re: plpython implementation |