Circularly referenced resultMap is filled with ancestor object even when columnPrefix is specified.

[ooknight]

mapper :

<resultMap id="user" type="User">
  <id property="id" column="id"/>
  <result property="name" column="name"/>
  <association property="superior" resultMap="user" columnPrefix="superior_" />
</resultMap>

<select id="find" parameterType="long" resultMap="user">
  select 1 as id, 'a' as name, 2 as superior_id , 'b' as superior_name from dual
</select>

java :

User user = dao.find(1L);
System.out.println("user.id : " + user.getId());
System.out.println("user.name : " + user.getName());
System.out.println("user.superior.id : " + user.getSuperior().getId());
System.out.println("user.superior.name : " + user.getSuperior().getName());

result :

[DEBUG] ==>  Preparing: select 1 as id, 'a' as name, 2 as superior_id , 'b' as superior_name from dual  [org.ufox.demo.dao.UserDao.find] 
[DEBUG] ==> Parameters:  [org.ufox.demo.dao.UserDao.find] 
[DEBUG] <==      Total: 1 [org.ufox.demo.dao.UserDao.find] 
user.id : 1
user.name : a
user.superior.id : 1
user.superior.name : a

[ooknight]

3.2.3 is ok, 3.2.4 - 3.2.7 has this bug
if (ancestorColumnPrefix.containsKey(nestedResultMapId)) {
rowKey = createRowKey(nestedResultMap, rsw, ancestorColumnPrefix.get(nestedResultMapId));
ancestorObject = ancestorObjects.get(rowKey);
}
ancestorColumnPrefix.get(nestedResultMapId)) return null, rowKey is same

[emacarron]

Hi @ooknight Thank you very much for the bug report.

Can you please submit a test?

[harawata]

Your resultMap contains circular reference.
Try this:

<resultMap id="user" type="User">
    <id property="id" column="id"/>
    <result property="name" column="name"/>
</resultMap>

<resultMap id="userAndSuperior" type="User" extends="user">
    <association property="superior" resultMap="user" columnPrefix="superior_" />
</resultMap>

<select id="find" parameterType="long" resultMap="userAndSuperior">
    select 1 as id, 'a' as name, 2 as superior_id , 'b' as superior_name from dual
</select>

[loicortola]

+1 for the issue:
Shouldn't mybatis be able to resolve such dependencies? It is not really a circular difference, because the columnprefix should allow nested objects to be populated within the same mapper.

I am having the same issue with a similar design in 3.2.7. I will use harawata's pattern as a workaround, but I think we are losing some of the flexibility of mappers (and columnPrefix becomes obsolete). --> Might be interesting to solve this

[harawata]

A test case contributed by another user in the forum seems to be the test case for this issue.
Reopening with the test case : 93757d2.