connect to ShardingSphere‐Proxy, if ShardingSphere‐Proxy does not create a database or does not add a resource, the client connection will fail? . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 8 adding a data source using DistSQL? . . . . . . . . . . . . . . . . . 459 8.5.2 DistSQL How to solve Resource [xxx] is still used by [Sin- gleTableRule]. exception when dropping a data source using DistSQL as the master table for the entire binding table since it specifies the sharding condition. All routing calculations will use only the policy of the primary table, then the sharding calculations for the

connect to ShardingSphere‐Proxy, if ShardingSphere‐Proxy does not create a database or does not add a resource, the client connection will fail? . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 8 adding a data source using DistSQL? . . . . . . . . . . . . . . . . . 498 8.5.2 DistSQL How to solve Resource [xxx] is still used by [Sin- gleTableRule]. exception when dropping a data source using DistSQL as the master table for the entire binding table since it specifies the sharding condition. All routing calculations will use only the policy of the primary table, then the sharding calculations for the

Shadow Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 7.5.3 Routing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 7.5.4 Shadow Judgment DistSQL is divided into RDL, RQL and RAL. • RDL (Resource & Rule Definition Language) responsible for the definition of resources and rules; • RQL (Resource & Rule Query Language) responsible for the query query of resources and rules; • RAL (Resource & Rule Administration Language) responsible for the added‐on administrator fea‐ ture of hint, transaction type switch, sharding execute planning and so on

Shadow Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 7.6.3 Routing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 7.6.4 Shadow Judgment connect to ShardingSphere‐Proxy, if ShardingSphere‐Proxy does not create a Schema or does not add a Resource, the client connection will fail? . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 7 adding a data source using DistSQL? . . . . . . . . . . . . . . . 350 7.8.19 [DistSQL] How to solve Resource [xxx] is still used by [Sin- gleTableRule]. exception when dropping a data source using DistSQL

Shadow Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 7.6.3 Routing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 7.6.4 Shadow Judgment connect to ShardingSphere‐Proxy, if ShardingSphere‐Proxy does not create a Schema or does not add a Resource, the client connection will fail? . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 7 adding a data source using DistSQL? . . . . . . . . . . . . . . . 362 7.8.19 [DistSQL] How to solve Resource [xxx] is still used by [Sin- gleTableRule]. exception when dropping a data source using DistSQL

as the master table for the entire binding table since it specifies the sharding condition. All routing calculations will use only the policy of the primary table, then the sharding calculations for the by modulo, the order primary key is a sharded field. If there is no sharded field in SQL, full routing will be executed, of which performance is poor. In addition to the support for single‐sharding fields operations is the sharding key + sharding algorithm, known as sharding strategy. Mandatory Sharding routing For the scenario where the sharded field is not determined by SQL but by other external conditions

as the master table for the entire binding table since it specifies the sharding condition. All routing calculations will use only the policy of the primary table, then the sharding calculations for the by modulo, the order primary key is a sharded field. If there is no sharded field in SQL, full routing will be executed, of which performance is poor. In addition to the support for single‐sharding fields operations is the sharding key + sharding algorithm, known as sharding strategy. Mandatory Sharding routing For the scenario where the sharded field is not determined by SQL but by other external conditions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Schema Routing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Routing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Check routing rules (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

value 10 to sharding 0 and value 11 to sharding 1, there will be 4 SQLs in Cartesian product after routing: SELECT i.* FROM t_order_0 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in WHERE o. order_id in (10, 11); With binding table configuration, there should be 2 SQLs after routing: SELECT i.* FROM t_order_0 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in ); If the routing algorithm is value % 2, when a logical database t_order corresponds to two physical databasest_order_0 and t_order_1, the SQL will be executed on t_order_1 after routing. The following

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Schema Routing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Routing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Check routing rules (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .