Hi all,

I'm like to be sure of something about the different inheritance strategy. If the subclasses are very sollicitated, wouldn't it be better to adopt a table per class hierarchy strategy rather than table per subclass because of the joint query between the root table and the "sub tables" ?

What could be the advantage of the second strategy?

Vladislav

With the second strategy you can put constraints on your columns (not null constraints for example). With the first strategy, if you have one attribute that is mandatory in one subclass but not present in another one, you cannot put the not-null constraint on the database column.
Another problem is if you have a lot of subclasses with a lot of differents attributes. This will lead in a very huge table, not maintanable.

Seb

Please, see the post "Hibernate and Inheritance"[1] and think.

[1] http://forum.hibernate.org/viewtopic.php?t=928586

[]s

Ary Junior