Entity inheritance mapping strategies,the joined subclass

Hi,

From Java EE tutorial, i was read that the joined subclass strategies could have a poor performance for extensive class hierarchies because need some joins to get the rows of the database.

I am developing an application that use three levels of entity inheritance and i would use this strategy for mapping my entities to my database schema, but is my first time that i do it and i don't know that three levels of inheritance could have poor performance.

From the point of view of yours experience, is a high level of inheritance (three class, main entity, another that extend it, and another extend) for use this strategy? what do you think that is the top level of inheritance for use joined subclass strategy for mapping my entities class?

thanks

[785 byte] By [kerulea] at [2007-11-27 5:07:37]
# 1
IMO, you should balance the number of distinct attributes in the subclasses against the inheritance level. If you only have one (or few) non-shared attributes in your subclasses, just go for the SingleTable approach.
mf125085a at 2007-7-12 10:26:45 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...