Re: Aggregates containing outer references don't work per - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Aggregates containing outer references don't work per
Date
Msg-id 3EDF768B.5060607@Yahoo.com
Whole thread Raw
In response to Re: Aggregates containing outer references don't work per spec  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> When we considered outervar1 as a constant, we could do the aggregate in
>> the subquery using computations, but when SUM(outervar1) is computed in
>> an above query, combining that with anything that is part of different
>> query level makes no sense to me because those variables might not even
>> exist at the level that aggregate is being computed.
> 
> Sure they will.  They can only be outer (up-level) references, else the
> parser would not have resolved them in the first place.
> 
> If you accept that SUM(localvar + outervar) is a sensible computation,
> then I think you must accept that SUM(outervar1 + outervar2) makes sense
> too.  It's actually the exact same computation, it's just being
> referenced from within a sub-query.

What is SUM(up1levelvar + up2levelsvar) considered to be? Would that be 
the same as SUM(localvar + outervar) one level up?


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Aggregates containing outer references don't work per spec
Next
From: "scott.marlowe"
Date:
Subject: Re: Broken RR?