pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mike Mascari <mascarm@mascari.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Re: [SQL] aliases break my query
Date: Fri, 26 May 2000 21:45:07 -0400
Message-ID: <392F28A3.7EB67B84@mascari.com> (raw)
References: <200005262343.TAA02242@candle.pha.pa.us>

Bruce Momjian wrote:
> 
> > "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?

How about a SET variable which allows PostgreSQL to reject any
queries which are not entirely within the specificaton; kind of
like -ansi -pedantic with gcc? Perhaps that's quite a bit of
work, but it seems quite valuable for developing portable
applications...Of course dependency on PostgreSQL extensions
isn't a bad thing either ;-)

Mike Mascari



view thread (15+ messages)  latest in thread

Message-ID: <392F28A3.7EB67B84@mascari.com>
Permalink:  ../392F28A3.7EB67B84@mascari.com/
Also on:    postgresql.org/message-id/392F28A3.7EB67B84@mascari.com

 · 

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: mascarm@mascari.com, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: [SQL] aliases break my query
  In-Reply-To: <392F28A3.7EB67B84@mascari.com>
  References: <200005262343.TAA02242@candle.pha.pa.us> <392F28A3.7EB67B84@mascari.com>

* 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