Re: [SQL] table aliasing problem with 6.5... - Mailing list pgsql-sql

From Bruce Momjian
Subject Re: [SQL] table aliasing problem with 6.5...
Date
Msg-id 199909281353.JAA16347@candle.pha.pa.us
Whole thread Raw
In response to Re: [SQL] table aliasing problem with 6.5...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
> 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?

I asked Thomas to regenerate the expected output.  I have too many other
differences to patch the files.  I can disable it for the time being if
Jan wants me to.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-sql by date:

Previous
From: Eric BASIER
Date:
Subject: Type of data that a function can return ?
Next
From: Bruce Momjian
Date:
Subject: Re: [SQL] table aliasing problem with 6.5...