This is a Hibnerate polymorphism question and a data model design question; they are intertwingled. I\'ve used Hibernate in the past, and have enjoyed it, but sometimes I find
This pattern is very common in Hibernate based datalayers. How it works internally is heavily based on which inheritance strategy is used.
When using table per class or table per subclass inheritance, a table for every subclass/class will be created. For example, in your case, you would have a table Fruit and two tables Apple
and Orange
, with foreign key references between Fruit and Apple/Orange. When requesting a single fruit (be it apple or orange) by ID, Hibernate will outer join the Fruit table with the Apple and Orange table. Each row will be transformed into an Apple or Orange depending on from which table the fields were retrieved.
Another possibility is to use discriminators. A single table Fruit
will be used which will contain a discriminator field (ex. fruit_type
taking values apple
and orange
). Depending on the value of this field, Hibernate will determine whether the corresponding object is an Apple or an Orange.
In your case, in the case of eager loading, when Hibernate loads the Note object it will eagerly fetch the corresponding Fruit and populate the fruit field with an instance of Apple or Orange accordingly.
In the case of lazy fetching, the fruit field will be a proxy implementing the Fruit interface. Until the actual fruit field is loaded its type is undetermined.
Hope this answers some of your queries.