From: Tom Lane <tgl@sss.pgh.pa.us>
To: Zeugswetter Andreas <andreas.zeugswetter@telecom.at>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Re: [SQL] aliases break my query
Date: Fri, 26 May 2000 17:34:28 -0400
Message-ID: <3661.959376868@sss.pgh.pa.us> (raw)
In-Reply-To: <002601bfc74b$3fda29c0$f823080a@sd.spardat.at>
References: <Pine.GSO.4.02A.10005261453420.12244-100000@Falk.DoCS.UU.SE>
<2392.959358366@sss.pgh.pa.us>
<002601bfc74b$3fda29c0$f823080a@sd.spardat.at>
"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?
regards, tom lane
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: tgl@sss.pgh.pa.us, andreas.zeugswetter@telecom.at, pgsql-hackers@postgresql.org
Subject: Re: [SQL] aliases break my query
In-Reply-To: <3661.959376868@sss.pgh.pa.us>
References: <Pine.GSO.4.02A.10005261453420.12244-100000@Falk.DoCS.UU.SE> <2392.959358366@sss.pgh.pa.us> <002601bfc74b$3fda29c0$f823080a@sd.spardat.at> <3661.959376868@sss.pgh.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