@OneToOne With Shared Primary Key, Revisited
@OneToOne With Shared Primary Key, Revisited
Take another look at @OneToOne with a shared primary key.
Join the DZone community and get the full member experience.
Join For FreeVerify, standardize, and correct the Big 4 + more– name, email, phone and global addresses – try our Data Quality APIs now at Melissa Developer Portal!
Long time ago, I wrote a post @OneToOne with shared primary key. Today I would like to return to this problem, with solution based on @MapsId annotation introduced in JPA 2.0
Again we have two entities: Primus and Secundus. Both entities have primary key using Long Java type. They are related 1-1, and Secundus should use the same primary key as Primus.
3 Years after my initial post they will look slightly different ;)
@Entity
@Table(name = "PRIMUS")
public class Primus {
public static Primus newInstance() {
Primus primus = new Primus();
primus.secundus = new Secundus(primus);
return primus;
}
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
@OneToOne(cascade = CascadeType.ALL, mappedBy = "primus")
private Secundus secundus;
Primus() {
super();
}
...
}Not much changed here, ;). Really important changes were made on the Secundus:
@Entity
@Table(name = "SECUNDUS")
public class Secundus {
@Id
private Long id;
@JoinColumn(name = "ID")
@OneToOne
@MapsId
private Primus primus;
Secundus() {
super();
}
public Secundus(Primus primus) {
this();
this.primus = primus;
}As you see, the @PrimaryKeyJoinColumn annotation is replaced with two annotations: @MapsId, which defines thatSecundus identifier will be determined by Primus identifier, and @JoinColumn, specifying which column in SECUNDUS table will be used for joining.
Nothing more is needed :) - JPA Provider should automatically ask Primus for its identifier, when persistingSecundus, as long as you take care of correct entities correlation, like in newInstance method of Primus.
Long live JPA 2.0+ ;) :)
Developers! Quickly and easily gain access to the tools and information you need! Explore, test and combine our data quality APIs at Melissa Developer Portal – home to tools that save time and boost revenue. Our APIs verify, standardize, and correct the Big 4 + more – name, email, phone and global addresses – to ensure accurate delivery, prevent blacklisting and identify risks in real-time.
Like This Article? Read More From DZone
Published at DZone with permission of Michal Jastak , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}