| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: onlyvalue aggregate (was: First Aggregate Funtion?) |
| Date: | 2015-11-02 09:10:15 |
| Message-ID: | CANP8+jLkiW=XNHnv-Ngg_xDPExsxPDXw9=DxRD1-Zf=CHyu+tw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2 November 2015 at 09:32, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
> On 28 October 2015 at 16:50, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> > Hi,
> >
> > Here's a patch for the aggregate function outlined by Corey Huinker in
> > CADkLM=foA_oC_Ri23F9PbfLnfwXFbC3Lt8bBzRu3=CB77G9_qw(at)mail(dot)gmail(dot)com .
>
> +1. I've wanted something like this a few times. Of the names
> suggested so far, I think I prefer "single_value", and yes I think it
> should work with NULLs.
>
+1
I think we should avoid using ONLY or VALUE within the names since those
already have other meanings in Postgres.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2015-11-02 10:59:55 | Re: onlyvalue aggregate (was: First Aggregate Funtion?) |
| Previous Message | Simon Riggs | 2015-11-02 09:01:55 | Re: eXtensible Transaction Manager API |