mybatis mapper 路径问题探究

首先我们来提出一个问题，如下mapper.xml文件，在调用mybatis（
sqlSessionTemplate.selectOne(statement, parameter)）执行sql的时候，statement如何传入可以找到对应的MappedStatement

<?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="${dbName}.table_name">


    <!--
    **************************************************************************
    * 根据key[主键ID]参数查询select操作.
    * @author Chen.Biao
    * @date 2020-11-16 04:03:46.
    * @Copyright(C): 2020 the author chen.biao All rights reserved.
    **************************************************************************
    -->
    <select id="selectByPrimaryKey" parameterType="java.lang.Integer" resultMap="BaseResultMap">
        SELECT
            'true' as QUERYID,
            <include refid="Base_Column_List" />
        FROM
            table_name
        WHERE
            id = #{id,jdbcType=INTEGER}
    </select>

   

</mapper>

答案是两个：

1. <mapper>.namespace+<select>.id
2. <select>.id   (在id全局不重复的情况下)

 

源码探究：

首先我们找到mybatis在构建开始的时候会把所有的MappedStatement放入自定义的map中

------org.apache.ibatis.builder.MapperBuilderAssistant 

public MappedStatement addMappedStatement(
      String id,
      SqlSource sqlSource,
      StatementType statementType,
      SqlCommandType sqlCommandType,
      Integer fetchSize,
      Integer timeout,
      String parameterMap,
      Class<?> parameterType,
      String resultMap,
      Class<?> resultType,
      ResultSetType resultSetType,
      boolean flushCache,
      boolean useCache,
      boolean resultOrdered,
      KeyGenerator keyGenerator,
      String keyProperty,
      String keyColumn,
      String databaseId,
      LanguageDriver lang,
      String resultSets) {

    if (unresolvedCacheRef) {
      throw new IncompleteElementException("Cache-ref not yet resolved");
    }

    id = applyCurrentNamespace(id, false);
    boolean isSelect = sqlCommandType == SqlCommandType.SELECT;

    MappedStatement.Builder statementBuilder = new MappedStatement.Builder(configuration, id, sqlSource, sqlCommandType)
        .resource(resource)
        .fetchSize(fetchSize)
        .timeout(timeout)
        .statementType(statementType)
        .keyGenerator(keyGenerator)
        .keyProperty(keyProperty)
        .keyColumn(keyColumn)
        .databaseId(databaseId)
        .lang(lang)
        .resultOrdered(resultOrdered)
        .resultSets(resultSets)
        .resultMaps(getStatementResultMaps(resultMap, resultType, id))
        .resultSetType(resultSetType)
        .flushCacheRequired(valueOrDefault(flushCache, !isSelect))
        .useCache(valueOrDefault(useCache, isSelect))
        .cache(currentCache);

    ParameterMap statementParameterMap = getStatementParameterMap(parameterMap, parameterType, id);
    if (statementParameterMap != null) {
      statementBuilder.parameterMap(statementParameterMap);
    }

    MappedStatement statement = statementBuilder.build();
    configuration.addMappedStatement(statement);
    return statement;
  }

 

 

再来看下这个自定义map的put方法

------org.apache.ibatis.session.Configuration

protected final Map<String, MappedStatement> mappedStatements = new StrictMap<MappedStatement>("Mapped Statements collection");



public void addMappedStatement(MappedStatement ms) {
    mappedStatements.put(ms.getId(), ms);
  }


public V put(String key, V value) {
      if (containsKey(key)) {
        throw new IllegalArgumentException(name + " already contains value for " + key);
      }
      if (key.contains(".")) {
        final String shortKey = getShortName(key);
        if (super.get(shortKey) == null) {
          super.put(shortKey, value);
        } else {
          super.put(shortKey, (V) new Ambiguity(shortKey));
        }
      }
      return super.put(key, value);
    }

你会发现在put方法中每次调用实际上放入了两个值。所以两种方式都能可以执行sql