lazyboyl opened a new issue #8677:
URL: https://github.com/apache/shardingsphere/issues/8677


   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
   ShardingSphere 5.x
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-JDBC
   ### Expected behavior
   Use Tk,Mybatis.updateByPrimaryKeySelective methods 
   ### Actual behavior
   case "Can not update sharding key, logic table: [t_user], column: [user_id]."
   ### Reason analyze (If you can)
   
![image](https://user-images.githubusercontent.com/49420893/102482300-f33f7f00-409d-11eb-8899-84a5d06ade93.png)
   The judgment is made here, but I suggest adding a judgment before the pre 
judgment. If the value of the updated partition key is the same as the value 
after the update, it will be released.
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   SQL: UPDATE t_user  SET user_id = user_id,user_name = ?,pwd = ? WHERE  
user_id = ?
    sharding rule: user_id % 4
   ### Example codes for reproduce this issue (such as a github link).
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to