对于双向的1-N
关联,也相当于就是N-1
关联,2者是一样的。
双向关联必须在2端都增加对实体的访问,N
的一端增加引用到关联实体属性,1
的一端增加集合属性,集合元素关联实体。
无连接表的双向1-N关联
N
端需要使用@ManyToOne
注解来修饰代表关联体的属性; 1
端需要使用@OneToMany
注解修饰。
对于双向的1-N关联映射,通常不应该允许1的一端控制关系联系,应该让N
的一端控制关联关系。因此在使用@OneToMany
注解时,指定mappedBy
属性, 一旦@OneToMany
、@OneToOne
、ManyToMany
指定了该属性,则表明当前实体不能控制关联关系,同时JoinColumn
、@JoinTable
修饰也将不允许使用。
例子:Person
实体对应多个Address
实体
Person
类:
@Entity
@Table(name = "person_inf")
public class Person {
@Id
@Column(name = "person_id")
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int id;
private String name;
private int age;
@OneToMany(targetEntity = Address.class, fetch = FetchType.LAZY, mappedBy = "person")
private Set<Address> addresses = new HashSet<>();
//省略set、get、构造函数
...
}
@OneToMany(targetEntity = Address.class, fetch = FetchType.LAZY, mappedBy = "person")
: 指定了mappedBy
,表明Person
实体不能控制关联关系(具体之后分析),其值为Address
类中Person
属性的名称。
Address
类:
@Entity
@Table(name = "address_inf")
public class Address {
@Id
@Column(name = "address_id")
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int addressId;
private String addressDetail;
@ManyToOne(targetEntity = Person.class, fetch = FetchType.LAZY)
@JoinColumn(name = "person_id", referencedColumnName = "person_id", nullable = false)
private Person person;
//省略set、get、构造函数
...
}
private Person person;
: 在Address
中增加一个关联实体的属性。@ManyToOne(targetEntity = Person.class, fetch = FetchType.LAZY)
: 指定类型和加载方式,加载方式默认就是LAZY
。@JoinColumn(name = "person_id", referencedColumnName = "person_id", nullable = false)
: 在当前表中增加一行外键列,指向Person
,表明当前行数据属于哪一个Person
。name
指定外键列名称;referencedColumnName
值为该Person
表的主键名称。
现在根据测试代码来明白mappedBy
作用:
session.beginTransaction();
Person person = new Person();
person.setName("sweat");
person.setAge(21);
person.getAddresses().add(new Address("浙江杭州"));
person.getAddresses().add(new Address("浙江宁波"));
session.save(person);
session.getTransaction().commit();
先看一下这组测试代码对应数据库的数据:
mysql> select * from person_inf;
+-----------+-----+-------+
| person_id | age | name |
+-----------+-----+-------+
| 1 | 21 | sweat |
+-----------+-----+-------+
1 row in set (0.00 sec)
mysql> select * from address_inf;
Empty set (0.00 sec)
Person_inf
: 表中成功的保存了数据,但是address_inf
表中没有任何数据,也就是说Person
实体的set
没有被持久化。这是因为我们指定了N
端来控制关联关系,也就是mappedBy = "person"
。
现在给出另一段测试代码:
session.beginTransaction();
Person person = new Person();
person.setName("sweat");
person.setAge(21);
//持久化person
session.save(person);
Address address = new Address("浙江杭州");
address.setPerson(person);
session.persist(address);
Address address2 = new Address("浙江宁波");
address2.setPerson(person);
session.persist(address2);
session.getTransaction().commit();
数据库中的数据:
mysql> select * from person_inf;
+-----------+-----+-------+
| person_id | age | name |
+-----------+-----+-------+
| 1 | 21 | sweat |
+-----------+-----+-------+
1 row in set (0.00 sec)
mysql> select * from address_inf;
+------------+---------------+-----------+
| address_id | addressDetail | person_id |
+------------+---------------+-----------+
| 1 | 浙江杭州 | 1 |
| 2 | 浙江宁波 | 1 |
+------------+---------------+-----------+
2 rows in set (0.00 sec)
address_inf
表成功的插入了数据。看第二段测试代码的片段:
session.save(person);
Address address = new Address("浙江杭州");
address.setPerson(person);
session.persist(address);
先持久化Person
,随后通过Address
实体添加Person
对象,然后持久化保存Address
对象。也就是说这里通过Address
实体来控制关联关系,所以能够成功持久化数据。
有连接表的双向1-N关联
1
端不需要改变,只要在N
端添加@JoinTable
注解修饰即可。
修改后的Address
代码:
@Entity
@Table(name = "address_inf")
public class Address {
@Id
@Column(name = "address_id")
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int addressId;
private String addressDetail;
@ManyToOne(targetEntity = Person.class, fetch = FetchType.LAZY)
@JoinTable(name = "person_address",
joinColumns = @JoinColumn(name = "address_id", referencedColumnName = "address_id", unique = true),
inverseJoinColumns = @JoinColumn(name = "person_id", referencedColumnName = "person_id"))
private Person person;
//省略set、get、构造函数
...
}
测试代码和之前的一样,直接看数据库数据:
mysql> select * from person_inf;
+-----------+-----+-------+
| person_id | age | name |
+-----------+-----+-------+
| 1 | 21 | sweat |
+-----------+-----+-------+
1 row in set (0.01 sec)
mysql> select * from address_inf;
+------------+---------------+
| address_id | addressDetail |
+------------+---------------+
| 1 | 浙江杭州 |
| 2 | 浙江宁波 |
+------------+---------------+
2 rows in set (0.00 sec)
mysql> select * from person_address;
+-----------+------------+
| person_id | address_id |
+-----------+------------+
| 1 | 1 |
| 1 | 2 |
+-----------+------------+
2 rows in set (0.00 sec)
通过person_address
实现person_inf
和address_inf
表的关联。