On Oct 1, 2008, at 12:12 AM, Gurjeet Singh wrote:
On Wed, Oct 1, 2008 at 9:39 AM, Tom Lane <[EMAIL PROTECTED]> wrote: "Gurjeet Singh" <[EMAIL PROTECTED]> writes:> On Wed, Oct 1, 2008 at 3:07 AM, Decibel! <[EMAIL PROTECTED]> 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!" );
Yeah, something like that would be very helpful.
Mail sent from my BlackLaptop device
Haha. +1 -- Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
