Hi all,

I have a situation in which inheritance is only meaningful on the object side: I'd like to write java code around the superclass, but I will only ever query for instances of a subclass. I don't want to have a table for the parent class, because I expect huge numbers of entries on the subclasses and would rather not index across all subclasses when I know my queries will be confined one.

One solution is to "hide" the inheritance from hibernate -- don't map the parent, map the subclasses as seperate classes. Is this correct, or is there some way to inform hibernate of the inheritance without having a parent table?

Thanks,
G

Well their are different type of Strategies for tackling inheritance in Hibernate.

* Table per Class Strategy:

* Single Table per Class Hierarchy Strategy:

* Joined Subclass Strategy:

Just go through http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.html

Read the Section : 2.2.4. Mapping inheritance

It seems what you want is mapping of only Concrete Classes.This way you have inheritance at Object side but hibernate will take care of mapping this inheritance to DB Schema.

thanks, that's exactly what I should do. I knew about hierarchy and subclass, but had not heard of table-per-concrete class.

Cheers,
G

Hey it helped you and you have not rated the post :(