Master Hibernate and JPA with Spring Boot in 100 Steps - Step 46 - JPA Inheritance Hierarchies and Mappings - Table Per

The video tutorial explains the table per class inheritance strategy in JPA, where each concrete subclass has its own table. It highlights that while this approach simplifies data insertion and retrieval, it leads to data redundancy as common columns are repeated across tables. The tutorial also demonstrates how data is retrieved using a union of tables and discusses the pros and cons of this strategy, including performance benefits and potential issues with having multiple tables for subclasses.

What is the main characteristic of table per class inheritance in JPA?

• Each concrete class has its own table.

• Each abstract class has its own table.

• Inheritance is not supported.

• All classes share a single table.

In table per class inheritance, what happens to the common columns?

• They are stored only in the parent class table.

• They are ignored.

• They are repeated in each subclass table.

• They are stored in a separate table.

How are employee details retrieved in table per class inheritance?

• Using a join operation.

• Using a split operation.

• Using a union operation.

• Using a merge operation.

What is a potential drawback of table per class inheritance?

• It is difficult to insert data.

• Common columns are repeated in multiple tables.

• It does not support abstract classes.

• It requires a complex retrieval process.

What is an advantage of using table per class inheritance?

• It eliminates the need for unions.

• It improves performance and ease of insertion.

• It reduces the number of tables.

• It simplifies the database schema.