From: | Richard Greenwood <richard(dot)greenwood(at)gmail(dot)com> |
---|---|
To: | darren(at)ontrenet(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: not quite a cross tab query... |
Date: | 2009-03-05 20:27:50 |
Message-ID: | ae9185aa0903051227r7ca5d4fcs86cca65156961bb3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Mar 5, 2009 at 12:27 PM, <darren(at)ontrenet(dot)com> wrote:
> Have you tried using "group by"?
Thanks, but that doesn't do it. If I group by ID I loose the CAT,
group by CAT I loose the ID, group by bith and that's just the base
table. Am I missing something?
Regards,
Rich
>> Hello pgsql listers,
>>
>> I've got a problem that is similar to, but I don't think identical to,
>> a cross tab query. My data looks like:
>> ID | CAT
>> 1 | A
>> 1 | B
>> 2 | A
>> 2 | C
>> So for each ID there may be many CAT (categories).
>> The client wants it to look like:
>> ID | CATS
>> 1 | A,B
>> 2 | A,C
>> Where each ID is unique in the results, and the CAT values are
>> concatenated with a comma separator.
>>
>> There are about 100 unique CAT values. They only way I can see to do
>> it is programatically with a for loop. But before I do that I wanted
>> to bounce it off the fine minds that inhabit this list.
>>
>> Thanks,
>> Rich
>>
>> --
>> Richard Greenwood
>> richard(dot)greenwood(at)gmail(dot)com
>> www.greenwoodmap.com
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>
>
--
Richard Greenwood
richard(dot)greenwood(at)gmail(dot)com
www.greenwoodmap.com
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Greenwood | 2009-03-05 20:28:44 | Re: not quite a cross tab query... |
Previous Message | Guido Ostkamp | 2009-03-05 20:19:10 | BufferSync() performance |