Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
0fada37f
Commit
0fada37f
authored
Jan 22, 2001
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update FAQ.
parent
7e091913
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
14 additions
and
11 deletions
+14
-11
doc/FAQ
doc/FAQ
+8
-6
doc/src/FAQ/FAQ.html
doc/src/FAQ/FAQ.html
+6
-5
No files found.
doc/FAQ
View file @
0fada37f
...
...
@@ -948,7 +948,8 @@ SELECT *
4.24) How do I do an outer join?
PostgreSQL 7.1 and later supports outer joins. Here are two examples:
PostgreSQL 7.1 and later supports outer joins using the SQL standard
syntax. Here are two examples:
SELECT *
FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
...
...
@@ -956,11 +957,12 @@ SELECT *
SELECT *
FROM t1 LEFT OUTER JOIN t2 USING (col);
These identical queries join t1.col to t2.col, and return any unjoined
rows in t1. A RIGHT join would return unjoined rows of table t2. A
FULL join would return unjoined rows from t1 and t2. The word OUTER is
optional and is assumed in LEFT, RIGHT, and FULL joins. Ordinary joins
are called INNER joins.
These identical queries join t1.col to t2.col, and also return any
unjoined rows in t1 (those with no match in t2). A RIGHT join would
add unjoined rows of t2. A FULL join would return the matched rows
plus all unjoined rows from t1 and t2. The word OUTER is optional and
is assumed in LEFT, RIGHT, and FULL joins. Ordinary joins are called
INNER joins.
In previous releases, outer joins can be simulated using UNION and NOT
IN. For example, when joining tab1 and tab2, the following query does
...
...
doc/src/FAQ/FAQ.html
View file @
0fada37f
...
...
@@ -1224,8 +1224,8 @@ Lobby your company to join W3C, see http://www.w3.org/Consortium
<H4><A
name=
"4.24"
>
4.24
</A>
) How do I do an
<I>
outer
</I>
join?
<BR>
</H4>
<P>
PostgreSQL 7.1 and later supports outer joins
. Here are two
examples:
</P>
<P>
PostgreSQL 7.1 and later supports outer joins
using the SQL
standard syntax. Here are two
examples:
</P>
<PRE>
SELECT *
FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
...
...
@@ -1235,9 +1235,10 @@ or
SELECT *
FROM t1 LEFT OUTER JOIN t2 USING (col);
</PRE>
These identical queries join t1.col to t2.col, and return any
unjoined rows in t1. A
<SMALL>
RIGHT
</SMALL>
join would return
unjoined rows of table t2. A
<SMALL>
FULL
</SMALL>
join would return
These identical queries join t1.col to t2.col, and also return any
unjoined rows in t1 (those with no match in t2). A
<SMALL>
RIGHT
</SMALL>
join would add unjoined rows of t2. A
<SMALL>
FULL
</SMALL>
join would return the matched rows plus all
unjoined rows from t1 and t2. The word
<SMALL>
OUTER
</SMALL>
is
optional and is assumed in
<SMALL>
LEFT
</SMALL>
,
<SMALL>
RIGHT
</SMALL>
, and
<SMALL>
FULL
</SMALL>
joins. Ordinary joins
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment