pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Zeugswetter Andreas <andreas.zeugswetter@telecom.at>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Re: [SQL] aliases break my query
Date: Fri, 26 May 2000 19:43:12 -0400 (EDT)
Message-ID: <200005262343.TAA02242@candle.pha.pa.us> (raw)
In-Reply-To: <3661.959376868@sss.pgh.pa.us>

> "Zeugswetter Andreas" <andreas.zeugswetter@telecom.at> writes:
> > I think we could get agreement to not allow implicit from entries 
> > if there is a from clause in the statement, but allow them if a from clause
> > is missing altogether. The patch did not distinguish the two cases.
> 
> Hmm, that's a thought.  Taking it a little further, how about this:
> 
> "Emit a notice [or error if you insist] when an implicit FROM item is
> added that refers to the same underlying table as any existing FROM
> item."
> 
> 95% of the complaints I can remember seeing were from people who got
> confused by the behavior of "FROM table alias" combined with a reference
> like "table.column".  Seems to me the above rule would catch this case
> without being obtrusive in the useful cases.  Comments?

Yes, I even added a define called FROM_WARN.  It was disabled, and never
enabled.  When can we enable it?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@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 (15+ messages)  latest in thread

Message-ID: <200005262343.TAA02242@candle.pha.pa.us>
Permalink:  ../200005262343.TAA02242@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200005262343.TAA02242@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: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, andreas.zeugswetter@telecom.at, pgsql-hackers@postgresql.org
  Subject: Re: [SQL] aliases break my query
  In-Reply-To: <200005262343.TAA02242@candle.pha.pa.us>
  References: <3661.959376868@sss.pgh.pa.us> <200005262343.TAA02242@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