From: nha <lyondif02@free.fr>
To: David Weilers <david@lionhead.nl>
Cc: PgSQL-sql <pgsql-sql@postgresql.org>
Subject: Re: Double aggregate problem
Date: Thu, 23 Jul 2009 03:23:40 +0200
Message-ID: <4A67BB9C.2040707@free.fr> (raw)
In-Reply-To: <200907222104.38931.peter_e@gmx.net>
References: <H00000670039e901.1248279381.lionhead2.lionhead.nl@MHS>
<200907222104.38931.peter_e@gmx.net>
Hello,
Le 22/07/09 20:04, Peter Eisentraut a écrit :
> On Wednesday 22 July 2009 19:16:21 David Weilers wrote:
>> I have the following query:
>>
>> select v.id, array_to_string(array_accum(s.name),', ') as sector ,
>> array_to_string(array_accum(p.name),', ') as provincie from tblvacature
>> v, tblaccount a , tblvacaturesector vs, tblsector s ,
>> tblvacatureprovincie vp, tblprovincie p where v.id = 11 and v.account =
>> a.id and vs.vacature = v.id and s.id = vs.sector and vp.vacature = v.id
>> and p.id = vp.provincie group by v.id, v.inserted order by v.inserted
>> desc
>>
>> That currently produces the following output:
>
> No one is going to be able to reproduce that without the table definitions and
> data.
>
Peter Eisentraut is right... The rewritten query I suggested is only
derived from your original query and implicit data definitions
(including constraints).
I would like to point 2 things about that rewritten proposed query:
- Column 'inserted' is likely missing in the 2nd subquery and in the
global join condition;
- Duplicity or even multiplicity of value s.name and/or p.name may
result depending on the keys of tables (as implicitly mentioned by Peter
Eisentraut).
Regards.
--
nha / Lyon / France.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: lyondif02@free.fr, david@lionhead.nl
Subject: Re: Double aggregate problem
In-Reply-To: <4A67BB9C.2040707@free.fr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox