jumanjihu opened a new issue, #32923:
URL: https://github.com/apache/shardingsphere/issues/32923
### Which version of ShardingSphere did you use?
5.3.2
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
shardingsphere-jdbc-core
### Expected behavior
different phone with diferent like query column encrypt value
### Actual behavior
some different phone with the same like query column encrypt value
### Reason analyze (If you can)
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
sql is just simple “batch insert into xxx” for already existed data, and
like query column uses CHAR_DIGEST_LIKE algrithm.
### Example codes for reproduce this issue (such as a github link).
sql code:
`phone_encrypt` varchar(64) DEFAULT NULL COMMENT '加密手机号',
`assisted_query_phone` varchar(64) DEFAULT NULL COMMENT '加密手机号查询辅助列',
`like_query_phone` varchar(64) DEFAULT NULL COMMENT '加密手机号模糊查询辅助列',
mybatis code :
<insert id="batchInsert">
INSERT INTO `user_new` (
<include refid="Columns" />
)
VALUES
<foreach collection="list" item="item" separator=",">
(
#{item.id,jdbcType=BIGINT},
#{item.userName,jdbcType=VARCHAR},
#{item.realName,jdbcType=VARCHAR},
#{item.displayName,jdbcType=VARCHAR},
#{item.displayCode,jdbcType=VARCHAR},
#{item.phone,jdbcType=VARCHAR},
xxxxxxx
</foreach>
</insert>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
