pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael J Davis <michael.j.davis@tvguide.com>
To: 'J_Shevland@TurnAround.com.au' <J_Shevland@TurnAround.com.au>
Cc: 'pgsql-sql@postgreSQL.org' <pgsql-sql@postgreSQL.org>
Subject: RE: [SQL] OUTER JOINS
Date: Tue, 20 Apr 1999 00:30:04 -0500
Message-ID: <93C04F1F5173D211A27900105AA8FCFC1453E5@lambic.prevuenet.com> (raw)

I don't think outer joins are planned for 6.5.  Possibly 6.6?

	-----Original Message-----
	From:	Joe Shevland [SMTP:J_Shevland@TurnAround.com.au]
	Sent:	Monday, April 19, 1999 9:33 PM
	To:	Michael J Davis
	Cc:	'pgsql-sql@postgreSQL.org'
	Subject:	Re: [SQL] OUTER JOINS

	Aha, I was wondering where they were dredged from :) Is 6.5 going to
	support OJ's?

	Michael J Davis wrote:
	> 
	>         *= and =* are Oracle syntax for outer joins.
	> 
	>                 -----Original Message-----
	>                 From:   Dan Janowski [SMTP:danj@3skel.com]
	>                 Sent:   Monday, April 19, 1999 7:27 AM
	>                 To:     J_Shevland@TurnAround.com.au
	>                 Cc:     pgsql-sql@postgreSQL.org
	>                 Subject:        Re: [SQL] OUTER JOINS
	> 
	>                 Thanks for giving it a stab. Looking at the
available
	>                 operators,
	>                 there is no =* or *= ops available. Although I am
curious
	>                 where it
	>                 comes from.
	> 
	>                 Dan
	> 
	>                 Joe Shevland wrote:
	>                 > ...
	>                 > select t1.value from table_one t1, table_two t2
where
	> t1.key = t2.key;
	>                 >
	>                 > So this would be a straight LEFT join in my
understanding.
	> Now, I'm
	>                 > venturing beyond my experience with PostgreSQL
here, but
	> you may be able
	>                 > to use the associated SQL syntaxes:
	>                 >
	>                 > select ... where t1.key *= t2.key
	>                 > select ... where t1.key =* t2.key
	>                 > ...
	>                 >
	>                 > Dan Janowski wrote:
	>                 > >
	>                 > > I've looked through the docs and mail lists
but I am
	> coming
	>                 > > up short on references for LEFT/RIGHT/FULL
OUTER JOIN
	>                 > > avalability
	>                 > > or functional workarounds. It seems that
PostgreSQL does
	>                 > > not have it.
	>                 > >
	>                 > > Any recommendations on how to aproximate the
	> functionality?
	>                 > >
	>                 > > As a curiosity, is there a problem with
supporting these
	>                 > > OUTER joins or is it merely on the list?
	>                 > >
	> 
	>                 --
	>                 Dan Janowski     danj@3skel.com       Triskelion
Systems,
	>                 Inc.     Bronx, NY

	-- 
	---------------------------------------------
	 ,-._|\  | Joe Shevland
	/      \ | Principal Consultant
	\_,--._/ | Turnaround Solutions Pty. Ltd.
	      v  | http://www.TurnAround.com.au
	---------------------------------------------
	Skate to where the puck is going and not to
	where it has been - Wayne Gretzky



view thread (38+ messages)  latest in thread

Message-ID: <93C04F1F5173D211A27900105AA8FCFC1453E5@lambic.prevuenet.com>
Permalink:  ../93C04F1F5173D211A27900105AA8FCFC1453E5@lambic.prevuenet.com/
Also on:    postgresql.org/message-id/93C04F1F5173D211A27900105AA8FCFC1453E5@lambic.prevuenet.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: michael.j.davis@tvguide.com, J_Shevland@TurnAround.com.au
  Subject: Re: [SQL] OUTER JOINS
  In-Reply-To: <93C04F1F5173D211A27900105AA8FCFC1453E5@lambic.prevuenet.com>
  References: <93C04F1F5173D211A27900105AA8FCFC1453E5@lambic.prevuenet.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