t_order_0 to t_order_9 in the instance above. Binding Table It refers to a group of sharding tables with the same sharding rules. When using binding tables in multi‐ table correlating query, you must t_order and t_order_item are both sharded by order_id, and use order_id to correlate, so they are binding tables with each other. Cartesian product correlation will not appear in the multi‐tables correlating FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key order_id routes value 10 to sharding

above. Binding Table It refers to the primary table and the joiner table with the same sharding rules. for example, t_order and t_order_item are both sharded by order_id, so they are binding tables with FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key order_id routes value 10 to sharding t_order_1 o JOIN t_order_item_1 i ON o.order_id=i.order_id 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

Sharding 27 Apache ShardingSphere document, v5.1.1 Binding Table It refers to a group of sharding tables with the same sharding rules. When using binding tables in multi‐ table correlating query, you must t_order and t_order_item are both sharded by order_id, and use order_id to correlate, so they are binding tables with each other. Cartesian product correlation will not appear in the multi‐tables correlating FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key order_id routes value 10 to sharding

t_order_0. Binding Table It refers to the primary table and the joiner table with the same sharding rules, for example, t_order and t_order_item are both sharded by order_id, so they are binding tables with FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key order_id routes value 10 to sharding t_order_1 o JOIN t_order_item_1 i ON o.order_id=i.order_id 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

binding-table-rules> 5.1. ShardingSphere-JDBC 71 Apache ShardingSphere document, v5.0.0 binding-table-rule logic-tables="t_order,t_order_item"/> binding-table-rules> shardingsphere.rules.sharding.binding-tables[0]= # 绑定表规则列表 spring.shardingsphere.rules.sharding.binding-tables[1]= # 绑定表规则列表 spring.shardingsphere.rules.sharding.binding-tables[x]= # 绑定表规则列表 spring.shardingsphere sharding.binding-tables[0]=t_user,t_user_detail # 绑定表 名称，多个表之间以逗号分隔 spring.shardingsphere.rules.sharding.binding-tables[1]= # 绑定表名称，多个表之间以逗号分 隔 spring.shardingsphere.rules.sharding.binding-tables[x]=

t_order_0 to t_order_9 in the previous example. Binding Table Refers to a set of sharded tables with consistent sharding rules. When using binding tables for multi‐ table associated query, a sharding to order_id and are correlated using order_id, the two tables are binding tables. The multi‐table associated queries between binding tables will not have a Cartesian product association, so the associated JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); In the case where no binding table relationships are being set, assume that the sharding key order_id routes the value 10 to

t_order_0 to t_order_9 in the previous example. Binding Table Refers to a set of sharded tables with consistent sharding rules. When using binding tables for multi‐ table associated query, a sharding to order_id and are correlated using order_id, the two tables are binding tables. The multi‐table associated queries between binding tables will not have a Cartesian product association, so the associated JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); In the case where no binding table relationships are being set, assume that the sharding key order_id routes the value 10 to

shardingsphere.rules.sharding.binding-tables[0]= # 绑定表规则列表 spring.shardingsphere.rules.sharding.binding-tables[1]= # 绑定表规则列表 spring.shardingsphere.rules.sharding.binding-tables[x]= # 绑定表规则列表 spring.shardingsphere sharding.binding-tables[0]=t_user,t_user_detail # 绑定表 名称，多个表之间以逗号分隔 spring.shardingsphere.rules.sharding.binding-tables[1]= # 绑定表名称，多个表之间以逗号分 隔 spring.shardingsphere.rules.sharding.binding-tables[x]= 名称 类型 说明 id 属性 Spring Bean Id table‐rules (?) 标签 分片表规则配置 auto‐table‐rules (?) 标签 自动化分片表规则配置 binding‐table‐rules (?) 标签 绑定表规则配置 broadcast‐table‐rules (?) 标签 广播表规则配置 default‐database‐strategy‐ref (

重复的 tableName 将无法被创建 Sharding Binding Table Rule CREATE SHARDING BINDING TABLE RULES(bindTableRulesDefinition [, bindTableRulesDefinition] ...) ALTER SHARDING BINDING TABLE RULES(bindTableRulesDefinition nition [, bindTableRulesDefinition] ...) DROP SHARDING BINDING TABLE RULES bindTableRulesDefinition: (tableName [, tableName] ... ) • ALTER 会使用新的配置直接覆盖数据库内的绑定表配置 Sharding Broadcast Table Rule CREATE Sharding Binding Table Rule CREATE SHARDING BINDING TABLE RULES ( (t_order,t_order_item), (t_1,t_2) ); ALTER SHARDING BINDING TABLE RULES ( (t_order,t_order_item) ); DROP SHARDING BINDING TABLE RULES;

shardingsphere.rules.sharding.binding-tables[0]= # 绑定表规则列表 spring.shardingsphere.rules.sharding.binding-tables[1]= # 绑定表规则列表 spring.shardingsphere.rules.sharding.binding-tables[x]= # 绑定表规则列表 spring.shardingsphere 绑定表规则，多组绑定规则使用数组形式配置 spring.shardingsphere.rules.sharding.binding-tables[0]=t_user,t_user_detail # 绑定表 名称，多个表之间以逗号分隔 spring.shardingsphere.rules.sharding.binding-tables[1]= # 绑定表名称，多个表之间以逗号分 5.1. ShardingSphere-JDBC ShardingSphere-JDBC 96 Apache ShardingSphere document, v5.1.1 隔 spring.shardingsphere.rules.sharding.binding-tables[x]= # 绑定表名称，多个表之间以逗号分 隔 # 广播表规则配置 spring.shardingsphere.rules.sharding.broadcast-tables= #