mybatis延迟加载

1.需求

1.1有一个订单表以及一个用户表,一个用户可以创建多个订单,现在需要查询出所有订单,但是订单所属的用户不能一起查询出来,当需要的时候再进行查询,这样就用到mybatis的延迟查询。

2.实现

2.1ordermapper.xml

     <!-- 实现延迟加载 -->
     <resultMap type="order" id="ordersUserLazyLoadingResultMap">
        <id column="id" property="id"/>
        <result column="user_id" property="user_id"/>
        <result column="number" property="number"/>
        <result column="create_time" property="create_time"/>
        <result column="note" property="note"/>
        <!-- property =Order里面的user变量  javatype =pojo类型  select=查询用户使用的statement column= 传递的参数  select不在同一个包下需要命名空间-->
        <association property="user" javaType="user" select="com.ssm.mapping.UserMapperDAO.findUserById" column="user_id">

        </association>
     </resultMap>
     <select id="findOrdersUserLazyLoading" resultMap="ordersUserLazyLoadingResultMap">
        select * from orders
     </select>

2.2usermapperdao.xml

<!-- ${}表示拼接sql字符串 根据姓名模糊查询用户 
        可能会造成sql注入为题,如果接收的参数为简单类型,只能为${value} 与 #{}不一样,可是使用任何名称
    -->
    <select id="findUserByName" parameterType="java.lang.String" resultType="com.ssm.model.User">
        SELECT * FROM USER WHERE USERNAME LIKE '%${value}%'
    </select>

2.3ordermapper.java

public List<Order> findOrdersUserLazyLoading();

2.4springmvc控制器

@RequestMapping(value="/lazyload",method=RequestMethod.GET)
    public String ordersUserLazyLoading(HttpServletRequest request)
    {
        List<Order> list = ordermapper.findOrdersUserLazyLoading();
        request.setAttribute("orderlist", list);
        return "order_detail";
    }

2.5mybatis配置文件

<settings>
        <!-- 开启延迟加载 -->
        <setting name="lazyLoadingEnabled" value="true"/>
        <!-- 是否主动加载 -->
        <setting name="aggressiveLazyLoading" value="false"/>
    </settings>
    <typeAliases>
        <!-- 批量定义别名 别名为类名 首字母大小写均可-->
        <package name="com.ssm.model"/>
    </typeAliases>
    <!-- 引入资源 -->

2.6jsp页面

<c:forEach var="order" items="${requestScope.orderlist}">
        <p>订单id:${order.id}</p>
        <p>订单number:${order.number}</p>
        <p>订单user_id:${order.user_id}</p>
        <p>订单create_time:${order.create_time}</p>
        <p>订单note:${order.note}</p>
        <p>用户名:${order.user.username}</p>
   </c:forEach>

3.结果

3.1控制台输出

DEBUG [http-bio-8080-exec-12] - DispatcherServlet with name 'springmvc' processing GET request for [/SSM/order/lazyload]
DEBUG [http-bio-8080-exec-12] - Mapping [/order/lazyload] to HandlerExecutionChain with handler [com.ssm.controller.OrderController@32bef7ff] and 1 interceptor
DEBUG [http-bio-8080-exec-12] - Last-Modified value for [/SSM/order/lazyload] is: -1
DEBUG [http-bio-8080-exec-12] - Invoking request handler method: public java.lang.String com.ssm.controller.OrderController.ordersUserLazyLoading(javax.servlet.http.HttpServletRequest)
DEBUG [http-bio-8080-exec-12] - Creating a new SqlSession
DEBUG [http-bio-8080-exec-12] - SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@50c31fd4] was not registered for synchronization because synchronization is not active
DEBUG [http-bio-8080-exec-12] - Fetching JDBC Connection from DataSource
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - JDBC Connection [com.mchange.v2.c3p0.impl.NewProxyConnection@11fe15ef] will not be managed by Spring
DEBUG [http-bio-8080-exec-12] - ==>  Preparing: select * from orders 
DEBUG [http-bio-8080-exec-12] - ==> Parameters: 
DEBUG [http-bio-8080-exec-12] - <==      Total: 3
DEBUG [http-bio-8080-exec-12] - Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@50c31fd4]
DEBUG [http-bio-8080-exec-12] - Returning JDBC Connection to DataSource
DEBUG [http-bio-8080-exec-12] - com.mchange.v2.async.ThreadPoolAsynchronousRunner@48a767dd: Adding task to queue -- com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@1ca4c610
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - Rendering view [org.springframework.web.servlet.view.JstlView: name 'order_detail'; URL [/WEB-INF/views/order_detail.jsp]] in DispatcherServlet with name 'springmvc'
DEBUG [http-bio-8080-exec-12] - Forwarding to resource [/WEB-INF/views/order_detail.jsp] in InternalResourceView 'order_detail'
DEBUG [http-bio-8080-exec-12] - Fetching JDBC Connection from DataSource
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - JDBC Connection [com.mchange.v2.c3p0.impl.NewProxyConnection@7122bae3] will not be managed by Spring
DEBUG [http-bio-8080-exec-12] - ==>  Preparing: SELECT * FROM USER WHERE id=? 
DEBUG [http-bio-8080-exec-12] - ==> Parameters: 1(Integer)
DEBUG [http-bio-8080-exec-12] - <==      Total: 1
DEBUG [http-bio-8080-exec-12] - Returning JDBC Connection to DataSource
DEBUG [http-bio-8080-exec-12] - com.mchange.v2.async.ThreadPoolAsynchronousRunner@48a767dd: Adding task to queue -- com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@77e0abe
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - Fetching JDBC Connection from DataSource
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - JDBC Connection [com.mchange.v2.c3p0.impl.NewProxyConnection@43e14471] will not be managed by Spring
DEBUG [http-bio-8080-exec-12] - ==>  Preparing: SELECT * FROM USER WHERE id=? 
DEBUG [http-bio-8080-exec-12] - ==> Parameters: 1(Integer)
DEBUG [http-bio-8080-exec-12] - <==      Total: 1
DEBUG [http-bio-8080-exec-12] - Returning JDBC Connection to DataSource
DEBUG [http-bio-8080-exec-12] - com.mchange.v2.async.ThreadPoolAsynchronousRunner@48a767dd: Adding task to queue -- com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@29fbdf8b
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - Fetching JDBC Connection from DataSource
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - JDBC Connection [com.mchange.v2.c3p0.impl.NewProxyConnection@671c4bc1] will not be managed by Spring
DEBUG [http-bio-8080-exec-12] - ==>  Preparing: SELECT * FROM USER WHERE id=? 
DEBUG [http-bio-8080-exec-12] - ==> Parameters: 10(Integer)
DEBUG [http-bio-8080-exec-12] - <==      Total: 1
DEBUG [http-bio-8080-exec-12] - Returning JDBC Connection to DataSource
DEBUG [http-bio-8080-exec-12] - com.mchange.v2.async.ThreadPoolAsynchronousRunner@48a767dd: Adding task to queue -- com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@50fee334
DEBUG [http-bio-8080-exec-12] - trace com.mchange.v2.resourcepool.BasicResourcePool@161a1f7f [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@514d00d3)
DEBUG [http-bio-8080-exec-12] - Successfully completed request
DEBUG [C3P0PooledConnectionPoolManager[identityToken->1hge8029

3.2结论

1.可以看到mybatis并没有一次性查询出订单以及所属用户,而是等到jsp页面取order的变量user时才发出的查询语句根据user_id查询用户名


### MyBatis 延迟加载配置及使用方法 #### 1. 全局延迟加载配置 MyBatis 提供了一个全局配置项来启用或禁用延迟加载功能。该配置位于 `mybatis-config.xml` 文件中,主要涉及两个参数:`lazyLoadingEnabled` 和 `aggressiveLazyLoading`。 - **`lazyLoadingEnabled`**: 控制是否开启延迟加载,默认值为 `false`。如果设置为 `true`,则会激活延迟加载机制。 - **`aggressiveLazyLoading`**: 当前已被废弃,在较新的版本中默认关闭激进模式。此参数决定属性未被访问时是否会触发加载操作[^1]。 以下是全局配置的示例: ```xml <settings> <setting name="lazyLoadingEnabled" value="true"/> <setting name="aggressiveLazyLoading" value="false"/> </settings> ``` #### 2. 局部延迟加载配置 除了全局配置外,还可以针对具体的 SQL 映射文件进行局部调整。这通常通过 `<association>` 或 `<collection>` 标签内的 `fetchType` 属性完成: - **`fetchType="lazy"`**: 启用特定字段的延迟加载- **`fetchType="eager"`**: 关闭指定字段的延迟加载并立即执行查询。 下面是一个典型的 XML 配置片段展示如何定义关联对象以及其加载方式: ```xml <select id="selectUserWithPosts" resultType="User"> SELECT * FROM users WHERE id = #{id} </select> <resultMap type="Post" id="postResultMap"> <id property="id" column="postId"/> <result property="title" column="postTitle"/> </resultMap> <association property="posts" javaType="List<Post>" resultMap="postResultMap" fetchType="lazy"/> ``` 上述代码表示当获取用户信息时不立刻加载帖子列表,而是在真正调用 `user.getPosts()` 方法时才发起额外请求去数据库读取相关内容[^2]。 #### 3. 加载顺序与注意事项 为了确保程序逻辑正确运行,开发者需要注意以下几个方面: - 如果存在复杂的嵌套关系,则可能需要多次网络交互才能完全填充整个对象图谱;因此建议仅对那些确实有必要减少初始加载量的部分实施懒加载策略。 - 某些情况下可能会遇到代理类生成失败或者无法序列化等问题,这时就需要重新审视设计方案是否存在不合理之处[^3]。 #### 示例代码演示 假设有一个简单的博客系统模型——每篇文章属于某个作者,并且每位作者可以撰写多篇文章。我们可以这样编写对应的 Mapper 接口和映射规则以支持文章详情页显示的同时按需加载评论区数据: ```java public interface ArticleMapper { @Select("SELECT * FROM articles WHERE article_id=#{articleId}") @Results({ @Result(id=true,property="articleId",column="article_id"), @Result(property="comments",column="article_id", many=@Many(select="findCommentsByArticleId",fetchType=FetchType.LAZY)) }) public Article getArticleById(int articleId); } @Select("SELECT * FROM comments WHERE article_id=#{articleId}") public List<Comment> findCommentsByArticleId(@Param("articleId") int articleId); ``` 以上 Java 注解形式同样实现了基于条件的选择性延后处理某些子集资源的需求[^4]。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值