表与表之间的关系有一对一,一对多(多对一),多对多等等,我们今天来讲一下表与表的最常见的一种关系,即一对多关系。
废话少说,直接上代码,已知一个用户对应多个联系人,但是一个联系人只能有一个用户。
首先,建表:
user表
linkman表
并且在多的一方设置外键
做到这里表的结构就完成了
第二步,建立实体类User.java和LinkMan.java
User.java
public class User {
private Long id;
private String name;
private Integer age;
private List<LinkMan> linkMans;
public User() {
super();
}
public User(String name, int age) {
this.name = name;
this.age = age;
}
public Long getId() {
return id;
}
public void setId(Long id) {
this.id = id;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
public Integer getAge() {
return age;
}
public void setAge(Integer age) {
this.age = age;
}
public List<LinkMan> getLinkMans() {
return linkMans;
}
public void setLinkMans(List<LinkMan> linkMans) {
this.linkMans = linkMans;
}
@Override
public String toString() {
return "User [id=" + id + ", name=" + name + ", age=" + age + ", linkMans=" + linkMans + "]";
}
LinkMan.java
public class LinkMan {
private Long id;
private String name;
private Integer age;
private User user;
public Long getId() {
return id;
}
public void setId(Long id) {
this.id = id;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
public Integer getAge() {
return age;
}
public void setAge(Integer age) {
this.age = age;
}
public User getUser() {
return user;
}
public void setUser(User user) {
this.user = user;
}
@Override
public String toString() {
return "LinkMan [id=" + id + ", name=" + name + ", age=" + age + ", user=" + user + "]";
}
}
这里需要注意一下,因为如果自接使用系统生成的tostring方法,就会报Exception in thread “main” java.lang.StackOverflowError,原因是在User.java中user的tostring方法中调用了linkman的tostring方法,如果你在linkMan的tostring方法中调用User的tostring方法,就会造成递归调用,最好造成栈内存溢出。
第三步:创建UserMapper.java LinkManMapper.java方法接口
UserMapper.java
public User select(Long id);
public User findUser(Long id);
LinkManMapper.java
public List<LinkMan> findByUid(Long id); //根据外键uid查询值
第四步:创建UserMapper.xml LinkManMapper.xml映射文件
UserMapper.xml
<mapper namespace="com.itheima.mapper.UserMapper">
<resultMap type="user" id="userResult">
<id property="id" column="id"/>
<result property="name" column="name"/>
<result property="age" column="age"/>
<collection property="linkMans" column="id" select="com.itheima.mapper.LinkManMapper.findByUid" />
</resultMap>
<select id="select" parameterType="long" resultMap="userResult">
select * from user where id = #{id}
</select>
<select id="findUser" parameterType="long" resultType="user">
select * from user where id = #{id}
</select>
</mapper>
LinkManMapper.xml
<mapper namespace="com.itheima.mapper.LinkManMapper">
<resultMap type="linkMan" id="linkManResult">
<id property="id" column="id"/>
<result property="name" column="name"/>
<result property="age" column="age"/>
<association property="user" column="uid" select="com.itheima.mapper.UserMapper.findUser" />
</resultMap>
<select id="findByUid" parameterType="long" resultMap="linkManResult">
select * from linkman where uid=#{id}
</select>
</mapper>
第四步:配置Mybatis-config.xml
<configuration>
<properties resource="c3p0.properties" />
<settings>
<setting name="lazyLoadingEnabled" value="true"/>
<setting name="aggressiveLazyLoading" value="false"/>
<setting name="lazyLoadTriggerMethods" value=""/>
</settings>
<typeAliases>
<typeAlias type="com.itheima.domain.User" alias="user" />
<typeAlias type="com.itheima.domain.LinkMan" alias="linkMan" />
</typeAliases>
<environments default="development">
<environment id="development">
<transactionManager type="JDBC" />
<dataSource type="com.itheima.pool.C3P0DataSource">
</dataSource>
</environment>
</environments>
<mappers>
<mapper resource="com/itheima/mapper/UserMapper.xml"/>
<mapper resource="com/itheima/mapper/LinkManMapper.xml"/>
</mappers>
</configuration>
至于为什么需要配置<setting》中的第三条配置,可以参考:
https://blog.csdn.net/hi_bigguy/article/details/84981120
最后一步,编写测试类test.java
UserMapper userMapper = sqlSession.getMapper(UserMapper.class);
LinkManMapper linkManMapper = sqlSession.getMapper(LinkManMapper.class);
User user = userMapper.select(1L);
System.out.println(user);
/*List<LinkMan> linkMan = linkManMapper.findByUid(1L);
for (LinkMan lk : linkMan) {
System.out.println(lk);
}*/
在执行3,4行代码的同时将mybatis-config.xml文件中的setttings注释掉,意味着不采用延迟加载机制,打印出来的结果是:
User [id=1, name=张三, age=23, linkMans=[LinkMan [id=1, name=张小小, age=23, user=张三], LinkMan [id=2, name=张大大, age=24, user=张三]]]
使用延迟加载的结果是:User [id=1, name=张三, age=23, linkMans=null]
执行5,6,7行代码的同时将settings注释,打印的结果是:
LinkMan [id=1, name=张小小, age=23, user=User [id=1, name=张三, age=23, linkMans=null]]
LinkMan [id=2, name=张大大, age=24, user=User [id=1, name=张三, age=23, linkMans=null]]
不注释settings的情况:
LinkMan [id=1, name=张小小, age=23, user=null]
LinkMan [id=2, name=张大大, age=24, user=null]
还有一种情况是在LinkManMapper.xml中的association改成
<association property="user" column="uid" select="com.itheima.mapper.UserMapper.select" />
并且将linkMan中的tostring方法改成:
public String toString() {
String userString=null;
if(user!=null) {
userString=user.getName();
}
return "LinkMan [id=" + id + ", name=" + name + ", age=" + age + ", user=" + userString + "]";
}