Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Database design for a EJB3/J2EE application

Re: Database design for a EJB3/J2EE application

From: Dennis Williams <oracledba.williams_at_gmail.com>
Date: Sun, 7 May 2006 21:29:17 -0500
Message-ID: <de807caa0605071929w75a59a0cpa8b308d886738830@mail.gmail.com>


Tim,

What you describe about PK is often a limitation of the O-O implementation. It isn't just something stupid that one person thought up. My suggestion would be to yield on this aspect. Now, there will be other aspects that you should resist. If the design gets too O-O, then it gets impossible to create reports. Try to champion a more "enterprise" approach, as opposed to a database schema that just implements this project. Otherwise once the project is complete, people will gripe that they can't create a report without a 20-table-join.

Dennis

--
http://www.freelists.org/webpage/oracle-l
Received on Sun May 07 2006 - 21:29:17 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US