MyBatis初級實戰之六:一對多關聯查詢

歡迎訪問個人GitHub

https://github.com/zq2599/blog_demosjava

內容:全部原創文章分類彙總及配套源碼,涉及Java、Docker、Kubernetes、DevOPS等;git

本篇概覽

  • 本文是《MyBatis初級實戰》系列的第六篇,繼續實踐從多表獲取數據;程序員

  • 回顧上一篇,我們實戰了多表關聯的一對一關係,以下圖所示,查找日誌記錄時,把對應的用戶信息查出:
    在這裏插入圖片描述github

  • 本篇要實踐的是一對多關係:查詢用戶記錄時,把該用戶的全部日誌記錄都查出來,邏輯關係以下圖:web

在這裏插入圖片描述

  • 在具體編碼實現一對多查詢時,分別使用聯表和嵌套兩種方式實現,每種方式都按照下圖的步驟執行:

在這裏插入圖片描述

源碼下載

  1. 若是您不想編碼,能夠在GitHub下載全部源碼,地址和連接信息以下表所示(https://github.com/zq2599/blog_demos):
名稱 連接 備註
項目主頁 https://github.com/zq2599/blog_demos 該項目在GitHub上的主頁
git倉庫地址(https) https://github.com/zq2599/blog_demos.git 該項目源碼的倉庫地址,https協議
git倉庫地址(ssh) git@github.com:zq2599/blog_demos.git 該項目源碼的倉庫地址,ssh協議
  1. 這個git項目中有多個文件夾,本章的應用在mybatis文件夾下,以下圖紅框所示:

在這裏插入圖片描述
3. mybatis是個父工程,裏面有數個子工程,本篇的源碼在relatedoperation子工程中,以下圖紅框所示:sql

在這裏插入圖片描述

準備數據

  1. 本次實戰,在名爲mybatis的數據庫中創建兩個表(和前面幾篇文章中的表結構如出一轍):user和log表;
  2. user表記錄用戶信息,很是簡單,只有三個字段:主鍵、名稱、年齡
  3. log表記錄用戶行爲,四個字段:主鍵、用戶id、行爲描述、行爲時間
  4. user和log的關係以下圖:

在這裏插入圖片描述
5. 建表和添加數據的語句以下:shell

use mybatis;

DROP TABLE IF EXISTS `user`;

CREATE TABLE `user` (
  `id` int(32) NOT NULL AUTO_INCREMENT,
  `name` varchar(32) NOT NULL,
  `age` int(32) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;

DROP TABLE IF EXISTS `log`;

CREATE TABLE `log` (
  `id` int(32) NOT NULL AUTO_INCREMENT,
  `user_id` int(32),
  `action` varchar(255) NOT NULL,
  `create_time` datetime not null,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;

INSERT INTO mybatis.user (id, name, age) VALUES (3, 'tom', 11);

INSERT INTO mybatis.log (id, user_id, action, create_time) VALUES (3, 3, 'read book', '2020-08-07 08:18:16');
INSERT INTO mybatis.log (id, user_id, action, create_time) VALUES (4, 3, 'go to the cinema', '2020-09-02 20:00:00');
INSERT INTO mybatis.log (id, user_id, action, create_time) VALUES (5, 3, 'have a meal', '2020-10-05 12:03:36');
INSERT INTO mybatis.log (id, user_id, action, create_time) VALUES (6, 3, 'have a sleep', '2020-10-06 13:00:12');
INSERT INTO mybatis.log (id, user_id, action, create_time) VALUES (7, 3, 'write', '2020-10-08 09:21:11');

關於多表關聯查詢的兩種方式

  • 多表關聯查詢的實現有聯表嵌套查詢兩種,它們的差別在Mybatis中體如今resultMap的定義上:
  1. 聯表時,resultMap內使用collection子節點,將聯表查詢的結果映射到關聯對象集合;
  2. 嵌套時,resultMap內使用association子節點,association的select屬性觸發一次新的查詢;
  • 上述兩種方式都能成功獲得查詢結果,接下來逐一嘗試;

聯表查詢

  1. 本篇繼續使用上一篇中建立的子工程relatedoperation
  2. 實體類UserWithLogs.java以下,可見成員變量logs是用來保存該用戶全部日誌的集合:
package com.bolingcavalry.relatedoperation.entity;

import io.swagger.annotations.ApiModel;
import io.swagger.annotations.ApiModelProperty;
import lombok.Data;
import lombok.NoArgsConstructor;
import java.util.List;

@Data
@NoArgsConstructor
@ApiModel(description = "用戶實體類(含行爲日誌集合)")
public class UserWithLogs {

    @ApiModelProperty(value = "用戶ID")
    private Integer id;

    @ApiModelProperty(value = "用戶名", required = true)
    private String name;

    @ApiModelProperty(value = "用戶地址", required = false)
    private Integer age;

    @ApiModelProperty(value = "行爲日誌", required = false)
    private List<Log> logs;
}
  1. 保存SQL的UserMapper.xml以下,先把聯表查詢的SQL寫出來,結果在名爲
    leftJoinResultMap的resultMap中處理:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
<mapper namespace="com.bolingcavalry.relatedoperation.mapper.UserMapper">

    <select id="leftJoinSel" parameterType="int" resultMap="leftJoinResultMap">
        select
            u.id as user_id,
            u.name as user_name,
            u.age as user_age,
            l.id as log_id,
            l.user_id as log_user_id,
            l.action as log_action,
            l.create_time as log_create_time

        from mybatis.user as u
                 left join mybatis.log as l
                           on u.id = l.user_id
        where u.id = #{id}
    </select>
</mapper>
  1. leftJoinResultMap這個resultMap是一對多的關鍵,裏面的collection將log的全部記錄映射到logs集合中:
<resultMap id="leftJoinResultMap" type="UserWithLogs">
        <id property="id" column="user_id"/>
        <result  property="name" column="user_name" jdbcType="VARCHAR"/>
        <result property="age" column="user_age" jdbcType="INTEGER" />
        <collection property="logs" ofType="Log">
            <id property="id" column="log_id"/>
            <result property="userId" column="log_user_id" jdbcType="INTEGER" />
            <result property="action" column="log_action" jdbcType="VARCHAR" />
            <result property="createTime" column="log_create_time" jdbcType="TIMESTAMP" />
        </collection>
    </resultMap>
  1. 接口定義UserMapper.java :
@Repository
public interface UserMapper {
    UserWithLogs leftJoinSel(int id);
}
  1. service層:
@Service
public class UserService {
    @Autowired
    UserMapper userMapper;

    public UserWithLogs leftJoinSel(int id) {
        return userMapper.leftJoinSel(id);
    }
}
  1. controller層的代碼略多,是由於想把swagger信息作得儘可能完整:
@RestController
@RequestMapping("/user")
@Api(tags = {"UserController"})
public class UserController {
    @Autowired
    private UserService userService;

    @ApiOperation(value = "根據ID查找user記錄(包含行爲日誌),聯表查詢", notes="根據ID查找user記錄(包含行爲日誌),聯表查詢")
    @ApiImplicitParam(name = "id", value = "用戶ID", paramType = "path", required = true, dataType = "Integer")
    @RequestMapping(value = "/leftjoin/{id}", method = RequestMethod.GET)
    public UserWithLogs leftJoinSel(@PathVariable int id){
        return userService.leftJoinSel(id);
    }
}
  1. 最後是單元測試,在前文建立的ControllerTest.java中新建內部類User用於user表相關的單元測試,可見封裝了一個私有方法queryAndCheck負責請求和驗證結果,後面的嵌套查詢也會用到:
@Nested
    @TestMethodOrder(MethodOrderer.OrderAnnotation.class)
    @DisplayName("用戶服務")
    class User {

        /**
         * 經過用戶ID獲取用戶信息有兩種方式:left join和嵌套查詢,
         * 從客戶端來看,僅一部分path不一樣,所以將請求和檢查封裝到一個通用方法中,
         * 調用方法只須要指定不一樣的那一段path
         * @param subPath
         * @throws Exception
         */
        private void queryAndCheck(String subPath) throws Exception {
            String queryPath = "/user/" + subPath + "/" + TEST_USER_ID;

            log.info("query path [{}]", queryPath);

            mvc.perform(MockMvcRequestBuilders.get(queryPath).accept(MediaType.APPLICATION_JSON))
                    .andExpect(status().isOk())
                    .andExpect(jsonPath("$.id").value(TEST_USER_ID))
                    .andExpect(jsonPath("$..logs.length()").value(5))
                    .andDo(print());
        }

        @Test
        @DisplayName("經過用戶ID獲取用戶信息(包含行爲日誌),聯表查詢")
        @Order(1)
        void leftJoinSel() throws Exception {
            queryAndCheck(SEARCH_TYPE_LEFT_JOIN);
        }
    }
  1. 執行上述單元測試方法leftJoinSel,獲得結果以下:

在這裏插入圖片描述

  1. 爲了便於觀察,我將上圖紅框中的JSON數據作了格式化,以下所示,可見log表中的五條記錄都被關聯出來了,做爲整個user對象的一個字段:
{
    "id": 3,
    "name": "tom",
    "age": 11,
    "logs": [
        {
            "id": 3,
            "userId": 3,
            "action": "read book",
            "createTime": "2020-08-07"
        },
        {
            "id": 4,
            "userId": 3,
            "action": "go to the cinema",
            "createTime": "2020-09-02"
        },
        {
            "id": 5,
            "userId": 3,
            "action": "have a meal",
            "createTime": "2020-10-05"
        },
        {
            "id": 6,
            "userId": 3,
            "action": "have a sleep",
            "createTime": "2020-10-06"
        },
        {
            "id": 7,
            "userId": 3,
            "action": "write",
            "createTime": "2020-10-08"
        }
    ]
}
  1. 以上就是經過聯表的方式獲取一對多關聯結果,接下來我們嘗試嵌套查詢;

嵌套查詢

  1. 嵌套查詢的基本思路是將屢次查詢將結果合併,關鍵點仍是在SQL和resultMap的配置上,先看嵌套查詢的SQL,在UserMapper.xml文件中,以下,可見僅查詢了user表,並未涉及log表:
<select id="nestedSel" parameterType="int" resultMap="nestedResultMap">
        select
            u.id as user_id,
            u.name as user_name,
            u.age as user_age
        from mybatis.user as u
        where u.id = #{id}
    </select>
  1. 上面的SQL顯示結果保存在名爲nestedResultMap的resultMap中,來看這個resultMap,以下,可見實體類的logs字段對應的是一個association節點,該節點的select屬性表明這是個子查詢,查詢條件是user_id
<!-- association節點的select屬性會觸發嵌套查詢-->
    <resultMap id="nestedResultMap" type="UserWithLogs">
        <!-- column屬性中的user_id,來自前面查詢時的"u.id as user_id" -->
        <id property="id" column="user_id"/>
        <!-- column屬性中的user_name,來自前面查詢時的"u.name as user_name" -->
        <result  property="name" column="user_name" jdbcType="VARCHAR"/>
        <!-- column屬性中的user_age,來自前面查詢時的"u.age as user_age" -->
        <result property="age" column="user_age" jdbcType="INTEGER" />
        <!-- select屬性,表示這裏要執行嵌套查詢,將user_id傳給嵌套的查詢 -->
        <association property="logs" column="user_id" select="selectLogByUserId"></association>
    </resultMap>
  1. 名爲selectLogByUserId的SQL和resultMap以下,即查詢log表:
<select id="selectLogByUserId" parameterType="int" resultMap="log">
        select
            l.id,
            l.user_id,
            l.action,
            l.create_time
        from mybatis.log as l
        where l.user_id = #{user_id}
    </select>

    <resultMap id="log" type="log">
        <id property="id" column="id"/>
        <result column="user_id" jdbcType="INTEGER" property="userId"/>
        <result column="action" jdbcType="VARCHAR" property="action"/>
        <result column="create_time" jdbcType="TIMESTAMP" property="createTime"/>
        <result column="user_name" jdbcType="VARCHAR" property="userName"/>
    </resultMap>
  1. 以上就是嵌套查詢的關鍵點了,接下來循序漸進的在LogMapper、LogService、LogController中添加方法便可,下面是LogController中對應的web接口,稍後會在單元測試中調用這個接口進行驗證:
@ApiOperation(value = "根據ID查找user記錄(包含行爲日誌),嵌套查詢", notes="根據ID查找user記錄(包含行爲日誌),嵌套查詢")
    @ApiImplicitParam(name = "id", value = "用戶ID", paramType = "path", required = true, dataType = "Integer")
    @RequestMapping(value = "/nested/{id}", method = RequestMethod.GET)
    public UserWithLogs nestedSel(@PathVariable int id){
        return userService.nestedSel(id);
    }
  1. 單元測試的代碼很簡單,調用前面封裝好的queryAndCheck方法便可:
@Test
        @DisplayName("經過用戶ID獲取用戶信息(包含行爲日誌),嵌套查詢")
        @Order(2)
        void nestedSel() throws Exception {
            queryAndCheck(SEARCH_TYPE_NESTED);
        }
  1. 執行單元測試的結果以下圖紅框所示,和前面的聯表查詢同樣:

在這裏插入圖片描述

  • 兩種方式的一對多關聯查詢都試過了,接下來看看二者的區別;

聯表和嵌套的區別

  1. 首先是聯表查詢的日誌,以下,只有一次查詢:
2020-10-21 20:25:05.754  INFO 15408 --- [           main] c.b.r.controller.ControllerTest          : query path [/user/leftjoin/3]
2020-10-21 20:25:09.910  INFO 15408 --- [           main] com.alibaba.druid.pool.DruidDataSource   : {dataSource-1} inited
2020-10-21 20:25:09.925 DEBUG 15408 --- [           main] c.b.r.mapper.UserMapper.leftJoinSel      : ==>  Preparing: select u.id as user_id, u.name as user_name, u.age as user_age, l.id as log_id, l.user_id as log_user_id, l.action as log_action, l.create_time as log_create_time from mybatis.user as u left join mybatis.log as l on u.id = l.user_id where u.id = ?
2020-10-21 20:25:10.066 DEBUG 15408 --- [           main] c.b.r.mapper.UserMapper.leftJoinSel      : ==> Parameters: 3(Integer)
2020-10-21 20:25:10.092 DEBUG 15408 --- [           main] c.b.r.mapper.UserMapper.leftJoinSel      : <==      Total: 5
  1. 再來看看嵌套查詢的日誌,兩次:
2020-10-21 20:37:29.648  INFO 24384 --- [           main] c.b.r.controller.ControllerTest          : query path [/user/nested/3]
2020-10-21 20:37:33.867  INFO 24384 --- [           main] com.alibaba.druid.pool.DruidDataSource   : {dataSource-1} inited
2020-10-21 20:37:33.880 DEBUG 24384 --- [           main] c.b.r.mapper.UserMapper.nestedSel        : ==>  Preparing: select u.id as user_id, u.name as user_name, u.age as user_age from mybatis.user as u where u.id = ?
2020-10-21 20:37:34.018 DEBUG 24384 --- [           main] c.b.r.mapper.UserMapper.nestedSel        : ==> Parameters: 3(Integer)
2020-10-21 20:37:34.041 DEBUG 24384 --- [           main] c.b.r.m.UserMapper.selectLogByUserId     : ====>  Preparing: select l.id, l.user_id, l.action, l.create_time from mybatis.log as l where l.user_id = ?
2020-10-21 20:37:34.043 DEBUG 24384 --- [           main] c.b.r.m.UserMapper.selectLogByUserId     : ====> Parameters: 3(Integer)
2020-10-21 20:37:34.046 DEBUG 24384 --- [           main] c.b.r.m.UserMapper.selectLogByUserId     : <====      Total: 5
2020-10-21 20:37:34.047 DEBUG 24384 --- [           main] c.b.r.mapper.UserMapper.nestedSel        : <==      Total: 1
  • 至此,MyBatis經常使用的多表關聯查詢實戰就完成了,但願能給您一些參考,接下來的文章,我們繼續體驗MyBatis帶給咱們的各類特性。

你不孤單,欣宸原創一路相伴

  1. Java系列
  2. Spring系列
  3. Docker系列
  4. kubernetes系列
  5. 數據庫+中間件系列
  6. DevOps系列

歡迎關注公衆號:程序員欣宸

微信搜索「程序員欣宸」,我是欣宸,期待與您一同暢遊Java世界...
https://github.com/zq2599/blog_demos數據庫

相關文章
相關標籤/搜索