Skip site navigation (1) Skip section navigation (2)

Re: JOINs in FROM...

From: Stoffel van Aswegen <Stoffelva(at)gmsi(dot)co(dot)za>
To: "PostgreSQL Mailing List (E-mail)" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: JOINs in FROM...
Date: 2001-09-19 05:49:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
FROM foo
LEFT JOIN (SELECT * FROM bar ... ON ...)

In your query you missed a 'SELECT' in the brackets.
I'm not sure if PostgreSQL supports LEFT JOINS - perhaps someone can

-----Original Message-----
From: ericnielsen(at)pop(dot)ne(dot)mediaone(dot)net
Sent: 17 September 2001 04:23
To: pgsql-novice(at)postgresql(dot)org
Subject: [NOVICE] JOINs in FROM...

I've been trying to use the JOIN syntax in the FROM clause instead of
burying all the joins in the WHERE.  (Does postgres actually support outer
joins now? the user manual seems to imply it does, which version do I need
as a minimum?)  The resulting query is much simpler than my old UNION SELECT
cascade, but I must have done something wrong because I get a parse error.

Here's the query and the error.(formatted for monotype)
SELECT ldr.peopleid, ldr.firstname, ldr.lastname,, 
       flw.peopleid, flw.firstname, flw.lastname, 
       FROM (people LEFT JOIN organizatios ON organization=orgid) AS ldr,
            (poeple LEFT JOIN organizatios ON organization=orgid) AS flw,
       WHERE ldr.peopleid=leader and flw.peopleid=follower 
       ORDER BY ldr.lastname, ldr.firstname, flw.lastname, flw.firstname;
Warning: PostgreSQL query failed: ERROR: parser: parse error at or near ","

1) What is the problem with my query?
2) Is there any good way to move the last two joins into the FROM?


mail2web - Check your email from the web at .

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

pgsql-novice by date

Next:From: Adam bultmanDate: 2001-09-19 16:38:41
Subject: Greetings.
Previous:From: Horst HerbDate: 2001-09-18 13:43:50
Subject: Re: Is postgreSql really suitable?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group