Message-ID: <371BF57E.65B22B6@TurnAround.com.au>
Date: Tue, 20 Apr 1999 13:33:18 +1000
From: Joe Shevland <J_Shevland@TurnAround.com.au>
Reply-To: J_Shevland@TurnAround.com.au
Organization: Turnaround Solutions Pty. Ltd.
MIME-Version: 1.0
To: Michael J Davis <michael.j.davis@tvguide.com>
CC: "'pgsql-sql@postgreSQL.org'" <pgsql-sql@postgreSQL.org>
Subject: Re: [SQL] OUTER JOINS
References: <93C04F1F5173D211A27900105AA8FCFC1453E2@lambic.prevuenet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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