Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!rpi!brutus.cs.uiuc.edu!usc!ucsd!ucbvax!ucdavis!csusac!unify!jeff From: jeff@unify.uucp (Jeff Mischkinsky) Newsgroups: comp.databases Subject: Re: outer join question Message-ID: Date: 15 Jan 90 21:01:20 GMT References: <1751@cod.NOSC.MIL> <257@sea375.UUCP> Reply-To: jeff@unify.UUCP (Jeff Mischkinsky) Distribution: usa Organization: Unify Corporation, Sacramento, CA, USA Lines: 29 In article <257@sea375.UUCP> dave@sea375.UUCP (David A. Wilson) writes: >From article <1751@cod.NOSC.MIL>, by dberg@cod.NOSC.MIL (David I. Berg): >> >> Use the SQL construct: select x,y,... from a OUTER b where....., >> like so: >> >> "select socsec, name, amount_owed from table1 t1, OUTER table2 t2 >> where t1.socsec = t2.socsec" >> >Is the 'outer' specifier in any ANSI SQL standard? I sure haven't seen it >in most RDBMS systems I have encountered. I believe a few exist that do >implement outer joins but the last SQL specification I saw did not include >it. If anyone working on the ANSI SQL standard reads this, I hope outer join >will become part of the ANSI SQL soon. All other work arounds for solving >outer join problems are usually slow and ugly(definitely not for anyone with >a weak stomach.). >-- > David A. Wilson > dave@sea375.uucp > ...uw-beaver!uw-entropy!quick!sigma!sea375!dave The current working draft for the "next" ANSI SQL standard (SQL2) contains outer join. In fact it allows you to specifiy your favorite variety-- left, right, full, and inner. -- Jeff Mischkinsky internet: jeff@unify.UUCP Unify Corporation ...!{csusac,pyramid}!unify!jeff 3870 Rosin Court voice: (916) 920-9092 fax: (916) 921-5340 Sacramento, CA 95834