From 505cdd5873aa101a58a80ee4bceb8000eb7f5a35 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 22 Jan 2001 06:27:41 +0000 Subject: Update FAQ. --- doc/src/FAQ/FAQ.html | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index aff8e80df06..2ef4f1eceee 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -1224,21 +1224,26 @@ Lobby your company to join W3C, see http://www.w3.org/Consortium
PostgreSQL 7.1 and later supports outer joins. Here is an - example:
+PostgreSQL 7.1 and later supports outer joins. Here are two + examples:
++ SELECT * + FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col); ++or
SELECT * FROM t1 LEFT OUTER JOIN t2 USING (col);- This will join t1.col to t2.col, and return any unjoined rows in t1 - with NULL values for t2 columns. 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.
In previous releases, outer joins can be simulated using
UNION and NOT IN. For example, when
joining tab1 and tab2, the following query does an
outer join of the two tables:
--
cgit v1.2.3