1.what?
resultMap可以实现高级映射(association,collection具备延迟加载功能)
需求:如果查询订单并且关联查询用户信息,如果先查询订单信息即可满足要求,当我们需要查询用户信息时再查询用户信息。
对把用户信息的按需查询就叫做延迟加载
延迟加载:先从单表查询(比多表关联查询速度快很多),需要时在从关联表中去关联查询
2.实现(使用association)
需要定义两个statement
查询订单并且关联查询用户信息
(1)只查询订单信息
SELECT * FROM orders
在查询订单的statement中使用association去延迟加载(执行)下面的statement(关联用户的用户信息)
(2)关联用户信息
通过上面查询到的user_id去关联用户信息
sql编写实现:
<!-- 查询订单关联查询用户,用户信息需要延迟加载 -->
<select id="findOrdersUserLazyLoading" resultMap="OrdersUserLazyLoadingResultMap">
SELECT * FROM orders
</select>
resultMap的延迟加载(使用association)实现:
<!-- 延迟加载的resultMap -->
<resultMap type="com.ddd.mybatis.pojo.Orders" id="OrdersUserLazyLoadingResultMap">
<!--对订单信息进行映射配置 -->
<id column="id" property="id"/>
<result column="user_id" property="userId"/>
<result column="number" property="number"/>
<result column="createtime" property="createtime"/>
<result column="note" property="note"/>
<!-- 实现对用户信息进行延迟加载
select:指定延迟加载需要执行的statement的id(是根据user_id查询用户信息的statement)
要使用userMapper.xml中findUserById完成根据用户id(user_id)用户信息的查询,如果findUserById不在本mapper中需要前边加namespace
column:订单信息中关联用户信息查询的列,是user_id
关联查询的sql理解为:
SELECT orders.*,
(SELECT username FROM USER WHERE orders.user_id = user.id)username,
(SELECT sex FROM USER WHERE orders.user_id = user.id)sex
FROM orders
-->
<association property="user" javaType="com.ddd.mybatis.pojo.User"
select="com.ddd.mybatis.mapper.UserMapper.findUserById" column="user_id">
<!-- 实现对用户信息进行延迟加载,注意不在同一mapper中要加命名空间 -->
</association>
</resultMap>
ps:这里使用的是association中的select指定延迟加载去执行的statement的id
执行顺序:先执行findOrdersUserLazyLoading,当需要时,在执行findUserById
3.接口方法:
//查询订单关联查询用户,用户信息是延迟加载
public List<Orders> findOrdersUserLazyLoading()throws Exception;
4.测试:
(1)只查询单表orders获得一个list
(2)遍历list,当调用orders中的getUser方法时,开始延迟加载
(3)调用UserMap.xml中调用findUserById获取订户信息
mybatis默认没有打开延迟加载,要在sqlMapConfig.xml中配置settings
<settings>
<!-- 打开延迟加载开关 -->
<setting name="lazyLoadingEnabled" value="true"/>
<!-- 将积极加载改变成消极加载,也就是需要时加载 -->
<setting name="aggressiveLazyLoading" value="false"/>
</settings>
测试代码:根据我们的思路来看控制台打印的顺序:
@Test
public void testFindOrdersUserLazyLoading() throws Exception {
SqlSession sqlSession=sqlSessionFactory.openSession();
//获取代理对象
OrdersMapperCustom ordersMapperCustom=sqlSession.getMapper(OrdersMapperCustom.class);
List<Orders> list=ordersMapperCustom.findOrdersUserLazyLoading();
System.out.println(list.size());
System.out.println("-----------11111111-----------");
for (Orders order : list) {
User user=order.getUser();
System.out.println(user);
}
sqlSession.close();
}
执行结果展示:
Preparing: SELECT * FROM orders
2017-07-18 18:23:59,491 [main] [com.ddd.mybatis.mapper.OrdersMapperCustom.findOrdersUserLazyLoading]-[DEBUG] ==> Parameters:
2017-07-18 18:23:59,760 [main] [com.ddd.mybatis.mapper.OrdersMapperCustom.findOrdersUserLazyLoading]-[DEBUG] <== Total: 5
5
-----------11111111-----------
2017-07-18 18:23:59,762 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Preparing: SELECT * FROM USER WHERE id=?
2017-07-18 18:23:59,762 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Parameters: 1(Integer)
2017-07-18 18:23:59,765 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] <== Total: 1
User [id=1, username=小明, sex=男, birthday=Fri Sep 09 00:00:00 CST 2011, address=北京市海淀区, ordersList=null]
2017-07-18 18:23:59,768 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Preparing: SELECT * FROM USER WHERE id=?
2017-07-18 18:23:59,768 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Parameters: 3(Integer)
2017-07-18 18:23:59,770 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] <== Total: 1
User [id=3, username=huauhua, sex=女, birthday=Mon Jul 17 00:00:00 CST 2017, address=河南郑州, ordersList=null]
2017-07-18 18:23:59,770 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Preparing: SELECT * FROM USER WHERE id=?
2017-07-18 18:23:59,771 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Parameters: 13(Integer)
2017-07-18 18:23:59,772 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] <== Total: 1
User [id=13, username=杰克, sex=男, birthday=Mon Jul 17 00:00:00 CST 2017, address=美国纽约, ordersList=null]
2017-07-18 18:23:59,772 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Preparing: SELECT * FROM USER WHERE id=?
2017-07-18 18:23:59,773 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Parameters: 4(Integer)
2017-07-18 18:23:59,774 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] <== Total: 1
User [id=4, username=小明星, sex=男, birthday=Sat Jul 09 00:00:00 CST 2011, address=北京市海淀区4, ordersList=null]
2017-07-18 18:23:59,775 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Preparing: SELECT * FROM USER WHERE id=?
2017-07-18 18:23:59,775 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] ==> Parameters: 6(Integer)
2017-07-18 18:23:59,778 [main] [com.ddd.mybatis.mapper.UserMapper.findUserById]-[DEBUG] <== Total: 1
User [id=6, username=大张伟, sex=男, birthday=Mon Jul 17 00:00:00 CST 2017, address=广州佛山, ordersList=null]
可以看出它首先执行的是单表查询,当我们使用foreach循环时,我们看到它执行了关联查询。
思考:
延迟加载它就是为了减轻数据库的负担
那如果不使用association怎么实现呢?
可以定义两个mapper方法:
(1)查询订单列表
(2)根据id查询用户信息
实现思路:先实现第一个mapper方法,在程序(一般是Service)中按需去执行第二个方法
也就是不使用框架我们也能实现。
这就是延迟加载的思想:按需
总之就是先查简单的表,在去按需执行关联查询。
以上!结束!