Date: Mon, 24 Mar 2003 07:12:35 -0800 (PST)
From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: "Correia, Carla" <Carla.Correia@logicacmg.com>
Cc: "'pgsql-sql@postgresql.org'" <pgsql-sql@postgresql.org>
Subject: Re: Complex outer joins?
In-Reply-To: 
 <0F232CC93A58D6119C1600B0D0799B8102338822@hamsrvmx03.logica.co.uk>
Message-ID: <20030324070821.Q24147-100000@megazone23.bigpanda.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 24 Mar 2003, Correia, Carla wrote:

>  My problem is joins. I've seen the syntax on joins and have sucessefully
> used SQLs with joins, but I've got some other big SQL statements using many
> and complex
>  joins.
> Simplified example:
>
>  select G.SELID, G.TEXT,
>  	L.ID as SELLEVELID , L.SELLEVEL, L.LEVELJOIN, L.LEVELTEXT,
>  	C.ID as KRITERIENFELDID, C.SELFLD
>   from  G,  L,  C
>   where
>  	and G.SELID = L.SELID (+)
>  	and L.SELID = C.SELID (+)
>  	and L.SELLEVEL = C.SELLEVEL (+)
>
> How can i write this in Postgres? As the problem is that I use one same
>  table for varios joins. This is a problem in Postgres. Any ideas?

I don't really understand the question, it looks like two levels of outer
join to me, the first between g and l using selid and the second between
that and c using selid and sellevel.  What do you mean "one same table for
various joins"?