Re: Bad error message - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: Bad error message
Date
Msg-id 65937bea0809302212s30a8c114sd4763e3b525e160f@mail.gmail.com
Whole thread Raw
In response to Re: Bad error message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bad error message
List pgsql-hackers
On Wed, Oct 1, 2008 at 9:39 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Gurjeet Singh" <singh.gurjeet@gmail.com> writes:
> On Wed, Oct 1, 2008 at 3:07 AM, Decibel! <decibel@decibel.org> wrote:
>> ERROR:  aggregates not allowed in WHERE clause

> No, the real issue is that you are referencing the outer table's column's
> max() in the inner query (correlated sub-query).

Yeah.  It's not easy to see how the software could guess your real
intentions here.  We could maybe offer a vaguely-worded HINT but I'm
not able to think of wording that would be very helpful.

Can we do something like this in the code:

    if( "level of the referenced column's  relation" != "level of the (sub)query being processed" )
        errhint( "The subquery may be unintentionally referencing an outer query's column!" );

Best regards,
--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com

EnterpriseDB      http://www.enterprisedb.com

Mail sent from my BlackLaptop device

pgsql-hackers by date:

Previous
From: Paul Schlie
Date:
Subject: Re: Block-level CRC checks
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Block-level CRC checks