pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Rowell <richard@bowmansystems.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Outer Join Syntax
Date: Wed, 01 Aug 2001 14:06:03 -0400
Message-ID: <10530.996689163@sss.pgh.pa.us> (raw)
In-Reply-To: <001f01c11abe$ebd29740$8301a8c0@RICHARD>
References: <001f01c11abe$ebd29740$8301a8c0@RICHARD>

"Richard Rowell" <richard@bowmansystems.com> writes:
> outer join syntax.  MS has some nice syntactical sugar with the *=/=*
> operators that Postgres dosen't seem to support.

Some of us view it as "nonstandard and broken", not as "nice syntactical
sugar" ;-).

> I'm just not grasping how one would accomplish the same using the SQL-92
> syntax.

SELECT ...
FROM ASSESSMENT_MEDICAL a
	LEFT JOIN AGENCIES ag ON a.Agency_creating = ag.Agency_id
	LEFT JOIN YESNO_TYPES02 y1 ON a.Health_prob = y1.Yesno_code
	LEFT JOIN ...
WHERE a.inactive != 'Y' AND a.Client_id = $Edit_Client_id;

While this is more typing, it's clear which conditions determine
joinability and which are filters on the overall result, which is a
critical semantic issue that the Oracle/MS syntax fails miserably on.
For example, suppose I want to add a constraint like y1.col3 = 'foo'.
Now, if there are no rows meeting that constraint for a given value of
a.Health_prob = y1.Yesno_code, does that mean I want to have
ASSESSMENT_MEDICAL rows with that Health_prob show up with nulls
substituted for the y1 fields?  Or does it mean that I don't want to see
those rows at all?  AFAICS there's no way to make that distinction with
the Oracle/MS approach.  With the standard syntax, you put the
additional constraint in ON in one case, and in WHERE in the other case.

The standard syntax also allows you to control the join order by
parenthesization, which is not so important for your star-query
example, but is critical if you want to join two outer-join results
together --- otherwise, you can't control which combinations result
in partially-NULL rows out, and which result in no rows out.

			regards, tom lane



view thread (4+ messages)

Message-ID: <10530.996689163@sss.pgh.pa.us>
Permalink:  ../10530.996689163@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10530.996689163@sss.pgh.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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, richard@bowmansystems.com
  Subject: Re: Outer Join Syntax
  In-Reply-To: <10530.996689163@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