From: Jeff Boes <jeff@endpoint.com>
To: pgsql-admin@postgresql.org
Subject: Re: outer joins
Date: Fri, 05 Aug 2005 17:31:22 -0400
Message-ID: <42F3DAAA.4030306@endpoint.com> (raw)
In-Reply-To: <BAY102-F1548EC8F7F13114369AE2FD1C70@phx.gbl>
References: <BAY102-F1548EC8F7F13114369AE2FD1C70@phx.gbl>
D Kavan wrote:
> There are 66 project id's in the project table and 3 rows in the
> project_members table for global_id 2915, but it only returns 3. I
> would think it should return 66 rows, with 63 of them having a null
> pm.project_id.
>
> SELECT
> p.project_id, pm.project_id
> FROM project p
> LEFT OUTER JOIN project_members pm ON p.project_id = pm.project_id
> where (pm.project_id is null or pm.global_id = 2915)
>
It would return 66, if all 66 p.project_id's were _missing_ from the set
of pm.project_id's.
A "LEFT JOIN" asks for all the rows in the left-hand table (p), joined
to all the matching or missing rows in the right-hand table (pm). Then
your "WHERE" clause filters all those but the missing ones OR the ones
with global_id 2915.
You need to check on the data with something like:
select distinct project_id from project;
select distinct project_id from project_members;
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-admin@postgresql.org
Cc: jeff@endpoint.com
Subject: Re: outer joins
In-Reply-To: <42F3DAAA.4030306@endpoint.com>
References: <BAY102-F1548EC8F7F13114369AE2FD1C70@phx.gbl> <42F3DAAA.4030306@endpoint.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