Re: Database design for a EJB3/J2EE application

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