Home > Java > javaTutorial > How to Map Composite Keys with JPA and Hibernate Using `@IdClass` or `@EmbeddedId`?

How to Map Composite Keys with JPA and Hibernate Using `@IdClass` or `@EmbeddedId`?

DDD
Release: 2024-12-11 04:55:10
Original
205 people have browsed it

How to Map Composite Keys with JPA and Hibernate Using `@IdClass` or `@EmbeddedId`?

Mapping Composite Keys with JPA and Hibernate

In the provided SQL schema, the Time table has a composite primary key consisting of levelStation and confPathID fields. Mapping this type of key in JPA and Hibernate requires special annotations to represent the compound primary key.

Using the IdClass Annotation

One option is to define a Java class for the composite key using the @IdClass annotation. The class should have fields corresponding to the primary key columns, as well as getters, setters, equals, and hashCode methods:

1

2

3

4

5

6

public class TimePK implements Serializable {

    private Integer levelStation;

    private Integer confPathID;

 

    // Getters, setters, equals, hashCode

}

Copy after login

The entity class is then annotated with @IdClass and the composite key object:

1

2

3

4

5

6

7

8

9

10

@Entity

@IdClass(TimePK.class)

class Time implements Serializable {

    @Id

    private Integer levelStation;

    @Id

    private Integer confPathID;

 

    // Other properties

}

Copy after login

Using the EmbeddedId Annotation

Alternatively, you can use the @EmbeddedId annotation to define a class containing the composite key:

1

2

3

4

5

6

7

@Embeddable

public class TimePK implements Serializable {

    private Integer levelStation;

    private Integer confPathID;

 

    // Getters, setters, equals, hashCode

}

Copy after login

The entity class is then annotated with @EmbeddedId and the embedded composite key object:

1

2

3

4

5

6

7

@Entity

class Time implements Serializable {

    @EmbeddedId

    private TimePK timePK;

 

    // Other properties

}

Copy after login

Differences between IdClass and EmbeddedId

Both @IdClass and @EmbeddedId allow mapping of composite primary keys. However, there are some minor differences:

  • @IdClass specifies that a unique combination of fields forms the primary key, but they do not have a distinct meaning.
  • @EmbeddedId suggests that the composite key is a meaningful entity in its own right.

The choice between @IdClass and @EmbeddedId depends on the specific semantics of your application.

The above is the detailed content of How to Map Composite Keys with JPA and Hibernate Using `@IdClass` or `@EmbeddedId`?. For more information, please follow other related articles on the PHP Chinese website!

source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template