Skip site navigation (1) Skip section navigation (2)

RE: Outer joins

From: "Michael S(dot) Kelly" <michaelk(at)axian(dot)com>
To: <kaiq(at)realtyideas(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: RE: Outer joins
Date: 2000-04-18 18:17:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
Actually found the answer to my question in Bruce Momjian's book.  I'm
shamefaced to say that I never considered UNION ALL solve the problem.



*  Michael S. Kelly
*  4800 SW Griffith Dr., Ste. 202
*  Beaverton, OR  97005 USA
*  voice: (503)644-6106 x122  fax: (503)643-8425
*  <michaelk(at)axian(dot)com>
*    Axian:  Software Consulting and Training

-----Original Message-----
From: kaiq(at)realtyideas(dot)com [mailto:kaiq(at)realtyideas(dot)com]
Sent: Tuesday, April 18, 2000 10:54 AM
To: Michael S. Kelly
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] Outer joins

why it is a problem at all, if you use sql so long? outer join
can be easily simulated.

On Tue, 18 Apr 2000, Michael S. Kelly wrote:

> I understand that outer joins are not supported in PostgreSQL.  I'm just
> starting my first PostgreSQL project, and have to admit that this concerns
> me.  Outer joins have come in handy, at some point, in almost every
> project I've ever worked on.  I guess I'd like to hear how you all work
> around this issue.
> Thanks,
> -=michael=-

In response to


pgsql-sql by date

Next:From: Bruce MomjianDate: 2000-04-18 18:29:48
Subject: Re: Outer joins
Previous:From: Tom LaneDate: 2000-04-18 18:02:02
Subject: Re: Mystery: functions are slow with group by, but...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group