From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <maillist@candle.pha.pa.us>
Cc: Howie <caffeine@toodarkpark.org>
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] table aliasing problem with 6.5...
Date: Tue, 28 Sep 1999 09:51:48 -0400
Message-ID: <402.938526708@sss.pgh.pa.us> (raw)
In-Reply-To: <199909280448.AAA01722@candle.pha.pa.us>
Bruce Momjian <maillist@candle.pha.pa.us> writes:
>> In a situation where you've got subselects, it may not be immediately
>> obvious which FROM list the entry got added to. I can't think of any
>> simple way of identifying that, however :-(
> Not sure how to handle that either. I could print the subquery level
> number, or I could say "in subquery" or even go fancy and do "in
> sub-sub-query" depending on the number of levels down.
That seems like a good idea; it won't help tell the difference between
two subqueries at the same level, but in a lot of practical cases it
would tell you what you needed to know, and it won't confuse a novice.
I like the "... in subquery", "... in sub-subquery", etc wording.
BTW, Jan was complaining that a number of the regress tests now "fail"
because they provoke this message. Should we just update the expected
outputs, or should we change the tests not to use the feature?
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, maillist@candle.pha.pa.us, caffeine@toodarkpark.org, pgsql-sql@hub.org
Subject: Re: [SQL] table aliasing problem with 6.5...
In-Reply-To: <402.938526708@sss.pgh.pa.us>
References: <199909280448.AAA01722@candle.pha.pa.us> <402.938526708@sss.pgh.pa.us>
* 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