Home >Java >javaTutorial >What is the \'Owning Side\' in Object-Relational Mapping (ORM)?
Understanding the "Owning Side" in ORM Mapping
In Object-Relational Mapping (ORM), the concept of "owning side" refers to the entity that manages the foreign key relationship in a database. This arises because relational databases do not inherently support bidirectional relationships, unlike object-oriented programming.
Necessity of an Owning Side
In ORM, the owning side is responsible for maintaining the integrity of a relationship by owning the foreign key that represents the other entity in the relationship. Without an owning side, each side of the relationship would require a foreign key, leading to unnecessary association tables and potential data duplication.
Ownership in Different Relationship Types
Example: One-to-Many Mapping with Owning Side
Consider the following Java example:
@Entity public class Person { @Id private Long id; @OneToMany(mappedBy = "person") private List<IdDocument> idDocuments; } @Entity public class IdDocument { @Id private Long id; @ManyToOne private Person person; }
In this example, Person is the owning side, as it contains the foreign key that references the IdDocument table. The mappedBy attribute in IdDocument indicates that the relationship is managed by the owning side.
Implications of Using mappedBy
Using mappedBy on the non-owning side shifts the responsibility of managing the relationship to the owning side. This means:
The above is the detailed content of What is the 'Owning Side' in Object-Relational Mapping (ORM)?. For more information, please follow other related articles on the PHP Chinese website!