291277058 edited a comment on issue #6918: URL: https://github.com/apache/shardingsphere/issues/6918#issuecomment-683626235
> But if the value of the sharding key is updated but still exists in the original instance (No data migration), then this row will be `dead`. Since users can not get this record forever. User can realize it just like I did.Forbiden will sacrifice freedom of application possibility.Now I has problem with 4.1.1 and after version.I can not update entity with jpa method becauth the sql contains shardingkey. If user can not realize they should use `@Query` annotation , they will block here and difficult to go farther, and they will think why they can't use `save` method, even more they think use the `save` method will not cause any problem as they nerver change the shardingkey. A compromise approach，use the entity manager , compare the cache entity's shardingkey value.If value changed forbiden the sql commit. ---------------------------------------------------------------- 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]
