Closed jumanjihu closed 1 month ago
Hi @jumanjihu, can you format your code and mysql result with markdown, it's hard to read the issue now.
Hi @jumanjihu, can you format your code and mysql result with markdown, it's hard to read the issue now.
ok
What is your configuration details?
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
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, for example:
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).
java code:
sql code:
mybatis code :