Is it possible to have multiple inheritance strategies in an inheritance heirarchy? This is primarly for use with EJB3 POJOs. It does seem valuable to be able to have something like:
Code:
BusinessObject
BasePart extends BusinessObject (joined with BusinessObject)
BaseRequirement extends BusinessObject (joined with BusinessObject)
MechanicalPart extends BasePart (separate table)
Motor extends MechanicalPart (sametable with MechanicalPart)
etc..
The reason for this is that the system I am designing will have a *lot* of polymorphism, and having it all in one table will be too much to manage. Each type may have a lot of new attributes as well and the sum will probably exceed the max number of columns if it is all in one table
Is this possible with hibernate (or should it be possible in a future version?)
or should I just take the perf hit for the joins? How bad is it really? I don't expect the inheritance heirarchy to go much deeper than ~10 levels but that is already quite deep if you have to join over 10 tables...
From what I can see it makes the sql visually more complicated, but it might speed things up significantly if I can choose where in the heirarchy to do the joins..
Thanks for any insight
Feint