RE: Outer Joins are Evil?

I agree with Tim's comment back to you that "In short, first design the
"what" and then implement the "how", and don't confuse the order."

Good design /should/ take data access mechanisms into consideration but
not, IMHO, attempt to avoid any such mechanisms entirely.  If I don't
want you to enter a dwelling through the front door, I can either build
the dwelling without a front door or I can put a sign out front telling
you to come around back.  If I put up the sign, I suggest a normally
desired path for you to take to enter, but I don't prohibit/eliminate
the front door access path under all circumstances.  Silly analogy
maybe, but I think you get the idea.  :)


Karen Morton
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Upcoming events at http://www.hotsos.com/education/schedule.html

 

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
ryan_gaffuri@xxxxxxxxxxx
Sent: Tuesday, August 31, 2004 9:06 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Outer Joins are Evil?


when you design an oltp system do you take outer joins inter
consideration and attempt to minimize them at the design level? 
tim gorman mentioned that he does not for datawarehouses. 

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: