291277058 commented on issue #6918: URL: https://github.com/apache/shardingsphere/issues/6918#issuecomment-683357827
> @291277058 Hi Thanks for your explanation and example. I guess you did a lot of work on this issue. > To value your work, I wanna catch your point. How to understand **shardingkey should not update value(not forbiden update in the sql,just forbiden update the value of the sharding key)**? > > If setting sharding key appears in the update items instead of where-condition like `set shardingID=xxx where 1=1`, is this SQL expected to be executed? Yes,it should be execude, there is no reason to block sql commit, even canbe hanppened like want update shardingkey,but the value still route into the same table.So of cause expected to be executed.Deside execute or not should in the bessnies application.Not in base compoment,Shardingsphere should simple as it canbe. Thanks for your kindness.This is a disscuess,it useful for me and my work is always be valueful for my self. ---------------------------------------------------------------- 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]
