[GitHub] [shardingsphere] LightShine commented on issue #5806: ShardingUpdateStatementValidator requires that the value of the sharding key in set-statement must be consistent with the where-statement

[GitBox <gi...@apache.org>]

LightShine commented on issue #5806:
URL: https://github.com/apache/shardingsphere/issues/5806#issuecomment-946404369


   > Looks master branch has the same logic:
   > 
   > ```
   > throw new ShardingSphereException("Can not update sharding key, logic table: [%s], column: [%s].", tableName, shardingColumn);
   > ```
   > 
   > @LightShine , could we just shard by `user_id`? Since `user_phone` is sharding column, if it's changeable, it'll cause data record redistribution.
   
   no. In our scenario, user_id and user_phone need to be used for sharding. Moreover, my problem is that the update sql should not determine the existence of the sharding key in the set-statament.


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org