December 08 2013 by Kevin Bowersox

The following tutorial details how to use the @Inheritance annotation in combination with the table per class strategy to map an inheritance relationship in an object model.  The tutorial discusses the differences between the table per class strategy and the single table strategy explored in the previous tutorial Inheritance with @Inheritance.  Also discussed are the limitations of the table per class strategy.

To follow along, download the base code used for this tutorial from this GitHub repository. Source code for the completed project can be downloaded by clicking the GitHub logo below.

Post a Comment
Kaylyn commented on January 17 2017 7:02 AM
That's an iniugnoes way of thinking about it.
Email Site
Madge commented on January 17 2017 3:45 AM
Inhgists like this liven things up around here.
Email Site
Mahaley commented on January 17 2017 2:44 AM
Arlcties like this are an example of quick, helpful answers.
Email Site
legion commented on December 09 2013 8:53 AM
Very nice and useful tutorial with real time bugs and fixes :) Now waiting for "Table per subclass".
Post a Comment