pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.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 11:07:18 -0400 (EDT)
Message-ID: <199909281507.LAA18974@candle.pha.pa.us> (raw)
In-Reply-To: <402.938526708@sss.pgh.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?

I just looked at it, and I woild be required to loop up through the
pstate->parentParseState counting how many times I can continue going
up, and creating an elog string on the fly to print.  Doesn't seem worth
it, does it?

-- 
  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, Pennsylvania 19026



view thread (12+ messages)  latest in thread

Message-ID: <199909281507.LAA18974@candle.pha.pa.us>
Permalink:  ../199909281507.LAA18974@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199909281507.LAA18974@candle.pha.pa.us

 · 

reply

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: maillist@candle.pha.pa.us, tgl@sss.pgh.pa.us, caffeine@toodarkpark.org, pgsql-sql@hub.org
  Subject: Re: [SQL] table aliasing problem with 6.5...
  In-Reply-To: <199909281507.LAA18974@candle.pha.pa.us>
  References: <402.938526708@sss.pgh.pa.us> <199909281507.LAA18974@candle.pha.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