tristaZero commented on issue #7703: URL: https://github.com/apache/shardingsphere/issues/7703#issuecomment-716465136
Hi, @heqiao Thanks for your kind explanation. Actually, the idea I mentioned before is not an optimal solution for `SET shardingKey`. If users really want to update shardingKey, shardingsphere should execute that update and move the actual row to the new target table. But for now, we can take it as a better solution to balance updating safety and JPA case. ---------------------------------------------------------------- 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]
