Master Hibernate and JPA with Spring Boot in 100 Steps - Step 47 - JPA Inheritance Hierarchies and Mappings-Joined

The video tutorial explains the 'table per class' inheritance strategy in database design, where each subclass has its own table, and a join is performed to retrieve subclass details. The tutorial demonstrates this with an example using an H2 console, showing how tables for employees, full-time employees, and part-time employees are structured and queried. It highlights the benefits of avoiding column duplication but notes the performance cost due to multiple joins. The tutorial concludes by summarizing the strategy's advantages and limitations, setting the stage for exploring other options in future lessons.

Discuss the performance implications of using the joined option in database design as mentioned in the text.

What challenges might arise if there are multiple types of employees in the database?