From: | Joe <dev(at)freedomcircle(dot)net> |
---|---|
To: | Steve Midgley <science(at)misuse(dot)org> |
Cc: | pgsql-sql(at)postgresql(dot)org, David Garamond <davidgaramond(at)gmail(dot)com> |
Subject: | Re: grouping/clustering query |
Date: | 2008-10-23 18:28:33 |
Message-ID: | 4900C251.5040005@freedomcircle.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Steve Midgley wrote:
>> # (invoiceid, txid)
>> (A, 1)
>> (A, 3)
>> (B, 1)
>> (B, 2)
>> (C, 5)
>> (D, 6)
>> (D, 7)
>> (E, 8)
>> (F, 8)
>>
>> For journalling, I need to group/cluster this together. Is there a SQL
>> query that can generate this output:
>>
>> # (journal: invoiceids, txids)
>> [A,B] , [1,2,3]
>> [C], [5]
>> [D], [6,7]
>> [E,F], [8]
>
> Hi Dave,
>
> I'm not following the logic here. A has 1,3 and B has 1,2. So why does
> the first line print:
>
>> [A,B] , [1,2,3]
>
> What's the rule that tells the query to output this way? Is it that
> all of B's values are between A's values?
From a purely accounting standpoint, since transaction 1 was applied to
both invoices A and B, you need to group the invoices so that you can
compare total invoiced against total paid.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Midgley | 2008-10-24 15:04:37 | Re: grouping/clustering query |
Previous Message | Oliveiros Cristina | 2008-10-23 18:00:54 | Re: Postgres-sql-php |