From: | "immersive(dot)excel(at)gmail(dot)com" <immersive(dot)excel(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | x3v0-pgsql(at)yahoo(dot)com, pgsql-general(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org> |
Subject: | Re: Seamless replacement to MySQL's GROUP_CONCAT function... |
Date: | 2013-08-05 17:55:59 |
Message-ID: | 51FFE72F.9090605@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ahh! I was looking for that in the documentation!! I believe that is not mentioned on the function documentation page. I had tried ANY that works for other SQLs, but it had barfed on it. Let me test it and post the more efficient code, if it works...
========================
On 08/05/2013 01:04 PM, Alvaro Herrera wrote:
> immersive(dot)excel(at)gmail(dot)com escribió:
>
>> Note: I found some close-but-no cigar aggregates shared online, but
>> they would not accept integer arguments, nor would they handle the
>> optionally furnished delimiter. People would suggesting casting the
>> argument to the pseudo-GROUP_CONCAT. Again: Rewrite perhaps hundreds
>> of queries?<br>
> I don't think you need all the variations; you should be able to make
> them all work with a single set of functions, taking ANYELEMENT instead
> of text/int8/int4 etc.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | immersive.excel@gmail.com | 2013-08-05 18:06:12 | Re: Seamless replacement to MySQL's GROUP_CONCAT function... |
Previous Message | Richard Broersma | 2013-08-05 17:15:08 | Re: Seamless replacement to MySQL's GROUP_CONCAT function... |