RE: SQL Gurus ...

Change your "where" to an "and" to make the b.event part of the left outer join and it will work as you're expecting. The "where" is being applied after the join is complete, so, has a different affect.

select count(*)
from table1 a left outer join table2 b
on a.email = b.email
and b.event = '2103SM'
order by attend;

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jon Paris
Sent: Thursday, March 11, 2021 7:27 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: SQL Gurus ...

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Can someone please explain how I can ever get a lower row count from a left outer join than the number of rows that exist in the left table?

select count(*)
from table1 a left outer join table2 b
on a.email = b.email
where b.event = '2103SM'
order by attend;

That returns query returns a count of 848 rows. There are 858 rows in table1! (left table). And just for fun an inner join also returns 848 rows.

Any ideas anyone? I thought it was an absolute that a left outer always returned all rows in the left table.


Jon Paris

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com