realbasic-nug
[Top] [All Lists]

Re: Learning SQL?

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Learning SQL?
From: Norman Palardy <palardyn at shaw dot ca>
Date: Tue, 11 May 2004 22:07:30 -0600
Delivered-to: realbasic-nug at lists dot realsoftware dot com
List-help: <mailto:realbasic-nug-request@lists.realsoftware.com?subject=help>
List-id: REALbasic NUG <realbasic-nug.lists.realsoftware.com>
List-post: <mailto:realbasic-nug@lists.realsoftware.com>
References: <BCC321CB dot 1A800%sunshine at public dot kherson dot ua> <a06100503bcc2fc44faac at [192 dot 168 dot 0 dot 101]> <75302068-A147-11D8-BD55-000A95A9544A at shaw dot ca> <2A6FA93B-A1AD-11D8-8070-000A95A072FC at sb dot org> <849D9F3A-A1EF-11D8-BD55-000A95A9544A at shaw dot ca> <DD2A39E4-A232-11D8-8070-000A95A072FC at sb dot org>

On May 9, 2004, at 9:33 PM, Kevin Ballard wrote:

Hrm. The documentation I saw called that simple a LEFT JOIN and it used the syntax

SELECT salesrepname, totalsales FROM SalesReps LEFT JOIN Sales ON SalesReps.salesrepID = Sales.salesrepID;

It had a similar RIGHT JOIN and never mentioned OUTER JOIN. What you're saying is a LEFT or RIGHT JOIN is really an OUTER JOIN without the OUTER keyword written?

The first one is a simple join and only gives results where there are matching rows in both tables.

A full out join will give a row for EACH row in both tables and have NULLS for values in the "other" columns that would have been present from the table that does not have a match

And yes. OUTER and INNER are optional
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

<Prev in Thread] Current Thread [Next in Thread>