Re: *** Unwanted OUTER join, please help ***
Posted in 2000
Topics: SQL Development & Query Writing, Server Administration
John would you agree that Informix forces the OUTER on you when using brackets? In article <3949129D.7162BAAA@bellsouth.net>, "Carlson@WHSmith" <carlson1@bellsouth.net> wrote: > spammers_suck@my-deja.com wrote: > > > > Forgive the reposting. I need an answer and want to change the subject > > line to attract more guru attention :) > > > > Its a strange thing. > > > > I want do : > > > > FROM a, outer b, outer c, (d, outer e) > > > > Informix insists that I do : > > > > FROM a, outer b, outer c, outer (d, outer e) > > > > But I don't want d to be an outer join with a ! It returns unwanted > > "extra" rows. I want it to be a "regular" join. > > > > Any ideas? > > > > Why this apparent limitation? > > > > Sent via Deja.com http://www.deja.com/ > > Before you buy. > > Could you post a copy of the SQL in question? Some times I've ended up > with double-sided joins only to find that there was an issue with the > joins in the WHERE clause. > > -- > John Carlson > Informix DBA > WHSmith USA > > #include std_disclaimer.h /* These are my opinions, not my company's > opinion */ > Sent via Deja.com http://www.deja.com/ Before you buy.
spammers_suck@my-deja.com wrote: > > John would you agree that Informix forces the OUTER on you when using > brackets? > That's why I want to see the SQL in question. When you use the parens, that gives Informix the basic understanding of how the tables relate. Whether or not the outer join is valid depends on the SQL. > In article <3949129D.7162BAAA@bellsouth.net>, > "Carlson@WHSmith" <carlson1@bellsouth.net> wrote: > > spammers_suck@my-deja.com wrote: > > > > > > Forgive the reposting. I need an answer and want to change the > subject > > > line to attract more guru attention :) > > > > > > Its a strange thing. > > > > > > I want do : > > > > > > FROM a, outer b, outer c, (d, outer e) > > > > > > Informix insists that I do : > > > > > > FROM a, outer b, outer c, outer (d, outer e) > > > > > > But I don't want d to be an outer join with a ! It returns > unwanted > > > "extra" rows. I want it to be a "regular" join. > > > > > > Any ideas? > > > > > > Why this apparent limitation? > > > > > > Sent via Deja.com http://www.deja.com/ > > > Before you buy. > > > > Could you post a copy of the SQL in question? Some times I've ended > up > > with double-sided joins only to find that there was an issue with the > > joins in the WHERE clause. > > > > -- > > John Carlson > > Informix DBA > > WHSmith USA > > > > #include std_disclaimer.h /* These are my opinions, not my > company's > > opinion */ > > > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- John Carlson Informix DBA WHSmith USA #include std_disclaimer.h /* These are my opinions, not my company's opinion */