You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/11/06 04:10:47 UTC

[GitHub] [shardingsphere] heqiao commented on issue #7703: Can not update sharding key, logic table: [**], column: [**]

heqiao commented on issue #7703:
URL: https://github.com/apache/shardingsphere/issues/7703#issuecomment-722801605


   > IMO, DONT UPDATE Sharding key SHOULD be a principle in SharidngSphere instead of an implicit configuration to point it.
   
   Agreed. The uses cases for updating sharding keys are rare and probably should reconsider the sharding strategy if it did happen. However, to be clear, this question is not asking for providing capability of updating sharding keys like #8006 . The title of the issue can be misleading. 
   
   This issue is about correctly interpreting JPA generated update sqls as sharding key is included in set clause with value unchanged, thus causing misunderstanding from sharding sphere that sharding key is being updated. It's not.
   
   I just wanted to clarify in case anyone was misled by the title. 


----------------------------------------------------------------
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:
users@infra.apache.org