Skip site navigation (1) Skip section navigation (2)

Re: Review: listagg aggregate

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Scott Bailey <artacus(at)comcast(dot)net>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Review: listagg aggregate
Date: 2010-01-26 06:59:35
Message-ID: 162867791001252259r211b9c93l41ea3daa729d0079@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2010/1/25 David E. Wheeler <david(at)kineticode(dot)com>:
> On Jan 25, 2010, at 6:12 AM, Pavel Stehule wrote:
>
>> I am not happy, I thing so we do bigger chaos then it is. But it
>> hasn't progress. So I agree with name string_agg. In this case isn't a
>> problem rename this function if somebody would.
>
> Could you not use CREATE AGGREGATE to create an alias named listagg if you needed it? Or are we limited to a single argument in that case?

we can, but without one common known name we will have a propriety name.

Pavel

>
> David
>
>
>
>

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2010-01-26 07:03:29
Subject: Re: tab completion for prepared transactions?
Previous:From: Peter EisentrautDate: 2010-01-26 06:40:04
Subject: Re: default_language

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group