Article:		Object-Relational Mapping with Apache Jakarta OJB
Subject:		Bogus Modelization
Date:		2003-01-15 03:54:35
From:		anonymous2
Sigh... No matter which mapping tool one use, if one cannot get its modelization right in the first place, it doesn't matter, isn't it? More to the point, Manager should not be a subclass of Employe. An Employe is simply a contact. A Manager is a role. An Employe could be a Janitor also. Are you going to modelize that by subclassing Employe? Duh. Looking forward to see how you modelize an Employe with multiple roles. I assume that's what multiple inheritance is for: bogus object model... Oh well...

Showing messages 1 through 1 of 1.

• Bogus Modelization
  2004-01-03 11:50:32  anonymous2 [View]
  
  
  Agreed! About a third of the way through I also realized that Manager is a role, not a subtype of an entity. That soured the example for me. Made me think that the third form, one table per class with foreign key to parent, as a relational schema, is a lot like an association schema anyway.