From: Ludwig Lim <lud_nowhere_man@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Mailing List <pgsql-sql@postgresql.org>
Subject: Re: Question on OUTER JOINS.
Date: Fri, 27 Jun 2003 23:16:18 -0700 (PDT)
Message-ID: <20030628061618.19440.qmail@web80510.mail.yahoo.com> (raw)
In-Reply-To: <16131.1056780183@sss.pgh.pa.us>
--- Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Ludwig Lim <lud_nowhere_man@yahoo.com> writes:
> > 1) Is the ON clause of an OUTER JOIN always
> > evaluated first before the WHERE clause?
>
> No; the planner will do whatever it thinks is the
> most efficient way
> (assuming it can prove that the reordering it wants
> to do won't change
> the query result).
If re-ordering does change the result, is the ON
clause evaluated first and the WHERE filters out the
result of the OUTER JOIN?
> > Is there a way to rewrite the query as a view
> such
> > that one can do:
>
> I'm really not clear on what you want here. Better
> example please?
>
Sorry for not making it that clear.
Is there way of rewritting :
SELECT a.status,
employee_id
FROM permission a LEFT JOIN
( SELECT * FROM employee WHERE employee_id
=5) as b ON (a.status = b.status)
WHERE status='test'
into a query that has no subselect in the FROM clause.
I mean can the query above be rewritten into
something like:
SELECT a.status,
b.employee_id
FROM permission a LEFT JOIN employee b ON
(a.status = b.status)
WHERE a.status = 'test' and
b.employee_id = 5;
Thank you very much,
ludwig
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: lud_nowhere_man@yahoo.com, tgl@sss.pgh.pa.us
Subject: Re: Question on OUTER JOINS.
In-Reply-To: <20030628061618.19440.qmail@web80510.mail.yahoo.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