AW: [HACKERS] Informix and OUTER join syntax

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "'PostgreSQL-development'" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: AW: [HACKERS] Informix and OUTER join syntax
Date: 2000-01-13 09:52:49
Message-ID: 219F68D65015D011A8E000006F8590C603FDC201@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Looking in the Informix manuals, I now see how they handle
> complex outer
> joins:
>
> SELECT *
> FROM tab1, OUTER(tab2, tab3)
> WHERE tab1.col1 = tab2.col1 AND
> tab2.col1 = tab3.col1
>
> It does the tab2, tab3 join first, then _outer_ joins to tab1.
> Interesting.

Ok, just to clarify:

this select gives at least one row for every row in tab1
if an inner join on tab2, tab3 does not give a match (tab1.col1=tab2.col1)
all columns of tab2 and tab3 are set to null for that row.

If that is what you said, I didn't understand it.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Karel Zak - Zakkr 2000-01-13 10:11:51 Re: [HACKERS] Status request for 7.0
Previous Message Kevin Lam 2000-01-13 09:37:48 Re: question about MS Access connect to Postgresql 6.5.2-1