• Hint Sharding Strategy HintShardingStrategy refers to the sharding strategy which get sharding values by hint rather than extracted from SQL. • None sharding strategy NoneShardingStrategy refers to ShardingSphere can be compatible with SQL in way of parsing SQL statements and extracting columns and values to shard. If SQL does not have sharding conditions, it is impossible to shard without full route Hint in ShardingSphere. Mechanism Apache ShardingSphere uses ThreadLocal to manage sharding key values. Users can program to add sharding conditions to HintManager, but the condition is only effective

creation_date) values (1, 1, ‘insert’, ‘2017‐08‐08’), (2, 2, ‘insert’, ‘2017‐08‐08’) ON DUPLICATE KEY UPDATE status = ‘init’; INSERT INTO t_order_item (order_id , user_id , sta‐ tus , creation_date)VALUES status = conv ert(to_base64(aes_encrypt(1, ‘key’)) USING utf8) ON DUPLICATE KEY UPDATE status = VALUES(status); INSERT INTO t_order SET order_id = 1, user_id = 1, status = CON‐ VERT(to_base64(aes_encrypt(1 t_order (`field1`, `field2`) VALUES (10, 1); 可以看到，上述 SQL 中并未包含自增主键，是需要数据库自行填充的。ShardingSphere 配置自增主键后， SQL 将改写为： INSERT INTO t_order (`field1`, `field2`, order_id) VALUES (10, 1, xxxxx); 改写后的 SQL 将在

AUTO_INCREMENT, NAME VARCHAR(20), age INT); INSERT INTO users(NAME, age) VALUES('Tom', 12); INSERT INTO users(NAME, age) VALUES('Jack', 11); 2.3. 添加 Mybatis 的配置文件 conf.xml insert into users(name, age) values(#{name}, #{age}); delete from users where 2. 注解的实现 1). 定义 sql 映射的接口 public interface UserMapper { @Insert("insert into users(name, age) values(#{name}, #{age})") public int insertUser(User user); @Delete("delete from users where id=#{id}")

ShardingSphere can be compatible with SQL in way of parsing SQL statements and extracting columns and values to shard. If SQL does not have sharding conditions, it is impossible to shard without full data Hint in ShardingSphere. Mechanism Apache ShardingSphere uses ThreadLocal to manage sharding key values. Users can program to add sharding conditions to HintManager, but the condition is only effective (column_list)] Subquery Stable supported when sharding keys are using in both subquery and outer query, and values of sharding keys are the same. For example: SELECT * FROM (SELECT * FROM t_order WHERE order_id

ShardingSphere can be compatible with SQL in way of parsing SQL statements and extracting columns and values to shard. If SQL does not have sharding conditions, it is impossible to shard without full data Hint in ShardingSphere. Mechanism Apache ShardingSphere uses ThreadLocal to manage sharding key values. Users can program to add sharding conditions to HintManager, but the condition is only effective 1 Subquery Stable supported when sharding keys are using in both subquery and outer query, and values of sharding keys are the same. For example: SELECT * FROM (SELECT * FROM t_order WHERE order_id

ShardingSphere can be compatible with SQL in way of parsing SQL statements and extracting columns and values to shard. If SQL does not have sharding conditions, it is impossible to shard without full data Hint in ShardingSphere. Mechanism Apache ShardingSphere uses ThreadLocal to manage sharding key values. Users can program to add sharding conditions to HintManager, but the condition is only effective (column_list)] Subquery Stable supported when sharding keys are using in both subquery and outer query, and values of sharding keys are the same. For example: SELECT * FROM (SELECT * FROM t_order WHERE order_id

is provided by the kernel when both the subquery and the outer query specify a shard key and the values of the slice key remain consistent. e.g: SELECT * FROM (SELECT * FROM t_order WHERE order_id = 1) support for subqueries and outer queries that do not both specify a sharding key or have inconsistent values for the sharding key. e.g: SELECT * FROM (SELECT * FROM t_order) o; SELECT * FROM (SELECT * FROM support list • INSERT SQL support or not INSERT INTO table (column,⋯) VALUES (value,⋯) support INSERT INTO table (column,⋯) VALUES (value,⋯),(value,⋯),⋯ support INSERT INTO table (column,⋯) SELECT column1

is provided by the kernel when both the subquery and the outer query specify a shard key and the values of the slice key remain consistent. e.g: SELECT * FROM (SELECT * FROM t_order WHERE order_id = 1) support for subqueries and outer queries that do not both specify a sharding key or have inconsistent values for the sharding key. e.g: SELECT * FROM (SELECT * FROM t_order) o; SELECT * FROM (SELECT * FROM support list • INSERT SQL support or not INSERT INTO table (column,⋯) VALUES (value,⋯) support INSERT INTO table (column,⋯) VALUES (value,⋯),(value,⋯),⋯ support INSERT INTO table (column,⋯) SELECT column1

is provided by the kernel when both the subquery and the outer query specify a shard key and the values of the slice key remain consistent. e.g: SELECT * FROM (SELECT * FROM t_order WHERE order_id = 1) support for subqueries and outer queries that do not both specify a sharding key or have inconsistent values for the sharding key. e.g: SELECT * FROM (SELECT * FROM t_order) o; SELECT * FROM (SELECT * FROM support list • INSERT SQL support or not INSERT INTO table (column,⋯) VALUES (value,⋯) support INSERT INTO table (column,⋯) VALUES (value,⋯),(value,⋯),⋯ support INSERT INTO table (column,⋯) SELECT column1

is provided by the kernel when both the subquery and the outer query specify a shard key and the values of the slice key remain consistent. e.g: SELECT * FROM (SELECT * FROM t_order WHERE order_id = 1) support for subqueries and outer queries that do not both specify a sharding key or have inconsistent values for the sharding key. e.g: SELECT * FROM (SELECT * FROM t_order) o; SELECT * FROM (SELECT * FROM ShardingSphere document, v5.2.1 SQL support or not INSERT INTO table (column,⋯) VALUES (value,⋯) support INSERT INTO table (column,⋯) VALUES (value,⋯),(value,⋯),⋯ support INSERT INTO table (column,⋯) SELECT column1