Hibernate Tip : How to map multiple entities to the same table

preview_player
Показать описание

One of the readers of my blog asked me this question: Some of our entities have a lot of attributes and we don’t need all of them in all use cases. Can I create a second entity that only maps a subset of the most commonly used attributes? Is there anything I should consider?

Yes, you can map two or more entities to the same database table. If you want to map the same database table to two entities, you should create a simple inheritance hierarchy. The superclass, in this example a class called AbstractAuthor, should be abstract and contain all attributes that are shared by both entities. You should map it as a mapped superclass so that it is not an entity itself.

If you like this video, please give me your thumbs up and share it with your friends and co-workers.

Like my channel? Subscribe!

Join the free Member Library:

Want to connect with me?

#Hibernate #JPA #HibernateTips
  1. Thorben Janssen
  2. map multiple entities to same table
  3. Hibernate Tip
  4. Hibernate
  5. entity mapping
  6. JPA
Рекомендации по теме
Hibernate Tip : 0:03:42

Hibernate Tip : How to create and initialize a database

Hibernate Tip: How 0:03:59

Hibernate Tip: How To Map an Entity to a Query

Hibernate Tip: How 0:03:27

Hibernate Tip: How to use a custom database sequence

Hibernate Tip - 0:02:38

Hibernate Tip - How to bootstrap Hibernate with Spring Boot

Hibernate Tips ‘n’ 0:45:48

Hibernate Tips ‘n’ Tricks - 15 Tips to solve common problems by Thorben Janssen

Hibernate Tip : 0:03:03

Hibernate Tip : How to avoid MultipleBagFetchException

Hibernate Tip: How 0:05:26

Hibernate Tip: How to map the latest element of an association

Hibernate Tip: How 0:03:36

Hibernate Tip: How to map a java.util.Date

Hibernate Tip: How 0:03:29

Hibernate Tip: How to map an entity attribute to an Optional

Hibernate Tip: How 0:02:23

Hibernate Tip: How to define schema and table names

Hibernate Tip: How 0:02:36

Hibernate Tip: How to use the QueryCache to avoid additional queries

Hibernate Tip: How 0:02:20

Hibernate Tip: How to access Hibernate APIs from JPA

Hibernate Tip: How 0:03:03

Hibernate Tip: How to order associated entities without writing a custom query

Hibernate Tip: How 0:03:08

Hibernate Tip: How to create a database setup script based on entity mappings

Hibernate Tip: How 0:04:41

Hibernate Tip: How to integrate an external query builder

Hibernate Tip - 0:03:33

Hibernate Tip - How to map an association to a java.util.Map

Hibernate Tip: How 0:02:50

Hibernate Tip: How to initialize lazy relationships within a query

Hibernate Tip: How 0:02:39

Hibernate Tip: How to automatically set an attribute before persisting it

Hibernate Tip: How 0:04:39

Hibernate Tip: How to map native query results to managed entities

Hibernate Tip: How 0:04:33

Hibernate Tip: How to persist a List of Strings as an ElementCollection

Hibernate Tips: How 0:04:58

Hibernate Tips: How to use Hibernate's native bootstrapping API

Hibernate Tip: How 0:02:59

Hibernate Tip: How to automatically validate entity attributes

Hibernate Tip - 0:03:31

Hibernate Tip - How to use pagination with JPQL

Hibernate Tip: How 0:04:08

Hibernate Tip: How to Call a Stored Procedure

Комментарии
Автор

Is there an increased risk of deadlocks due to using the 2 entities if they are only for queries?

lavinahum
Автор

And how to map multiple linked entities to the different tables

igordryagunov
Автор

Great video thanks !. Would this be the same to JPA? I have a problem where I need to map compatible computer parts that are compatible with each other. What is the best? To create two different entities ComputerPart and ComputerPartCompatible with @OneToMany? Or I keep ComputerPart Entity and map it to itself with @ManyToMany?

markkuuss