fix(mcp): 修正物业所属销售富化永远为空(Map key 被驼峰化)
根因:SQL 别名用 property_id/user_id/user_name,而 MyBatis 的 mapUnderscoreToCamelCase=true 会把结果 Map 的 key 转成 propertyId/userId/userName, 代码按 "property_id" 取值永远 null → 富化静默跳过,sale_user_id 恒为空。 修复: - 别名改为无下划线的 pid/uid/uname,绕开驼峰转换 - 单测补两条并锁住:取到 userId → sale_user_id;缺失时回落 create_id (此前构造器新增 AgentMapper 参数,测试未同步,已一并修正) 验证:SyncEntitiesTest 26 例全过。
This commit is contained in:
@@ -24,7 +24,9 @@ public interface ProperytMapper extends BaseMapper<Properyt> {
|
||||
* <p>来源是物业表的 userId / userName 两列(实体未映射,故用显式 SQL)。
|
||||
* 独立查询 + 调用方容错:列名或数据异常只丢归属,不影响 properties 变更流。</p>
|
||||
*/
|
||||
@Select("<script>SELECT id AS property_id, userId AS user_id, userName AS user_name"
|
||||
// 别名刻意用无下划线的名字:MyBatis 的 mapUnderscoreToCamelCase 会把
|
||||
// property_id → propertyId,导致按 "property_id" 取值永远为 null。
|
||||
@Select("<script>SELECT id AS pid, userId AS uid, userName AS uname"
|
||||
+ " FROM properyt WHERE id IN"
|
||||
+ " <foreach collection='ids' item='id' open='(' separator=',' close=')'>#{id}</foreach>"
|
||||
+ "</script>")
|
||||
|
||||
@@ -76,13 +76,13 @@ public class PropertiesSyncEntity extends AbstractSyncEntity implements SyncEnti
|
||||
}
|
||||
if (!ids.isEmpty()) {
|
||||
for (Map<String, Object> owner : properytMapper.selectPropertyOwners(ids)) {
|
||||
Object pid = owner.get("property_id");
|
||||
Object pid = owner.get("pid");
|
||||
if (pid == null) {
|
||||
continue;
|
||||
}
|
||||
Long propertyId = Long.valueOf(String.valueOf(pid));
|
||||
Object uid = owner.get("user_id");
|
||||
Object uname = owner.get("user_name");
|
||||
Object uid = owner.get("uid");
|
||||
Object uname = owner.get("uname");
|
||||
if (uid != null) {
|
||||
ownerIds.put(propertyId, String.valueOf(uid));
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user