Javatpoint Logo



Javatpoint Logo

Table Per Concrete class using Annotation

In case of Table Per Concrete class, tables are created per class. So there are no nullable values in the table. Disadvantage of this approach is that duplicate columns are created in the subclass tables.

Here, we need to use @Inheritance(strategy = InheritanceType.TABLE_PER_CLASS) annotation in the parent class and @AttributeOverrides annotation in the subclasses.

@Inheritance(strategy = InheritanceType.TABLE_PER_CLASS) specifies that we are using table per concrete class strategy. It should be specified in the parent class only.

@AttributeOverrides defines that parent class attributes will be overriden in this class. In table structure, parent class table columns will be added in the subclass table.

The class hierarchy is given below:

table per concrete class
The table structure for each table will be as follows:

Table structure for Employee class

table per concrete class

Table structure for Regular_Employee class

table per concrete class

Table structure for Contract_Employee class

table per concrete class

Example of Table per concrete class

In this example we are creating the three classes and provide mapping of these classes in the employee.hbm.xml file.

1) Create the Persistent classes

You need to create the persistent classes representing the inheritance. Let's create the three classes for the above hierarchy:


2) Add mapping of hbm file in configuration file

File: hibernate.cfg.xml

The property is defined for creating automatic table in the database.

3) Create the class that stores the persistent object

In this class, we are simply storing the employee objects in the database.


Next TopicTable Per Subclass

Share this page

facebook twitter google plus pinterest tumbler

Latest 4 Tutorials