Re: [SQL] table aliasing problem with 6.5...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Howie <caffeine(at)toodarkpark(dot)org>, pgsql-sql(at)hub(dot)org
Subject: Re: [SQL] table aliasing problem with 6.5...
Date: 1999-09-28 13:51:48
Message-ID: 402.938526708@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)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

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Eric BASIER 1999-09-28 13:52:42 Type of data that a function can return ?
Previous Message Bruce Momjian 1999-09-28 12:55:06 Re: [SQL] pg_dumpall + psql -e template1