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 2022/04/17 02:55:03 UTC

[GitHub] [shardingsphere] Glowdable commented on issue #16880: why did we need SingleTableRule?

Glowdable commented on issue #16880:
URL: https://github.com/apache/shardingsphere/issues/16880#issuecomment-1100792322

   It's not wrong. I think that Sharding and read-write spilt  are the basic functions of ShardingSphere.
   
   We have to make sure the basic functionality is usable and user-friendly before extending other functionality.
   In other words, we cannot sacrifice the availability or performance of basic functions for some unimportant or infrequently used functions.
   We can do a survey to see how many people use encrypt rewriting or query optimization.
   And how many people are willing to sacrifice the performance and usability of basic functions for these functions.
   
   Moreover,why can't we provide a choice,only want to use the core functions, then we provide a better performance and more user-friendly implementation, and it is also optional to be willing to sacrifice the availability of some core functions for other functions


-- 
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