Distributed Primary Key Motivation In the development of traditional database software, the automatic sequence generation technology is a basic requirement. All kinds of databases have provided corresponding requirement, such as MySQL auto‐increment key, Oracle auto‐increment sequence and so on. It is a tricky problem that there is only one sequence generated by different data nodes after sharding. Auto‐increment UUID and others) relying on some particular algorithms to generate unrepeated keys or introducing sequence generation services. We have provided several built‐in key generators, such as UUID, SNOWFLAKE

Distributed Primary Key Motivation In the development of traditional database software, the automatic sequence generation technology is a basic requirement. All kinds of databases have provided corresponding requirement, such as MySQL auto‐increment key, Oracle auto‐increment sequence and so on. It is a tricky problem that there is only one sequence generated by different data nodes after sharding. Auto‐increment UUID and others) relying on some particular algorithms to generate unrepeated keys or introducing sequence generation services. We have provided several built‐in key generators, such as UUID, SNOWFLAKE

Distributed Primary Key Motivation In the development of traditional database software, the automatic sequence generation technology is a basic requirement. All kinds of databases have provided corresponding requirement, such as MySQL auto‐increment key, Oracle auto‐increment sequence and so on. It is a tricky problem that there is only one sequence generated by different data nodes after sharding. Auto‐increment UUID and others) relying on some particular algorithms to generate unrepeated keys or introducing sequence generation services. We have provided several built‐in key generators, such as UUID, SNOWFLAKE

ShardingSphere document, v5.2.0 primary key generator is not used. keyGeneratorName: # Distributed sequence algorithm name defaultDatabaseStrategy: standard: shardingColumn: # Sharding column name sh (+): # Distributed sequence algorithm name type: # Distributed sequence algorithm type props: # Property configuration of distributed sequence algorithm - !READWRITE_SPLITTING dataSources: table-strategy.xxx= # Omit # Distributed sequence strategy configuration spring.shardingsphere.rules.sharding.tables..key-generate-strategy. column= # Distributed sequence column name spring.shardingsphere

Distributed Primary Key Motivation In the development of traditional database software, the automatic sequence generation technology is a basic requirement. All kinds of databases have provided corresponding requirement, such as MySQL auto‐increment key, Oracle auto‐increment sequence and so on. It is a tricky problem that there is only one sequence generated by different data nodes after sharding. Auto‐increment UUID and others) relying on some particular algorithms to generate unrepeated keys or introducing sequence generation services. We have provided several built‐in key generators, such as UUID, SNOWFLAKE

ShardingSphere document, v5.2.1 primary key generator is not used. keyGeneratorName: # Distributed sequence algorithm name defaultDatabaseStrategy: standard: shardingColumn: # Sharding column name sh (+): # Distributed sequence algorithm name type: # Distributed sequence algorithm type props: # Property configuration of distributed sequence algorithm - !READWRITE_SPLITTING dataSources: table-strategy.xxx= # Omit # Distributed sequence strategy configuration spring.shardingsphere.rules.sharding.tables..key-generate-strategy. column= # Distributed sequence column name spring.shardingsphere

child node is the sharding item sequence number, starting from zero and ending with the total number of shards minus one. The child node of the sharding item sequence number stores detailed information shardingItemParameters: The sequence numbers and parameters of the Sharding items are separated by equal sign, and multiple key‐value pairs are separated by commas. The Sharding sequence number starts from 0 divided, the redundant sharding item that cannot be divided will be added to the server with small sequence number in turn. For example: 1. If there are 3 job servers and the total sharding count is 9, each

default, the auto-increment primary key generator is not used. keyGeneratorName: # Distributed sequence algorithm name defaultDatabaseStrategy: standard: shardingColumn: # Sharding column name sh (+): # Distributed sequence algorithm name type: # Distributed sequence algorithm type props: # Property configuration of distributed sequence algorithm - !ENCRYPT encryptors: < char(9), c_phone char(16), c_since timestamp, c_middle char(2), c_data varchar(500) ); create sequence bmsql_hist_id_seq; create table bmsql_history ( hist_id integer, h_c_id integer, h_c_d_id integer

default, the auto-increment primary key generator is not used. keyGeneratorName: # Distributed sequence algorithm name defaultDatabaseStrategy: standard: shardingColumn: # Sharding column name sh (+): # Distributed sequence algorithm name type: # Distributed sequence algorithm type props: # Property configuration of distributed sequence algorithm - !ENCRYPT encryptors: < char(9), c_phone char(16), c_since timestamp, c_middle char(2), c_data varchar(500) ); create sequence bmsql_hist_id_seq; create table bmsql_history ( hist_id integer, h_c_id integer, h_c_d_id integer

If your database table uses an IDENTITY, AUTO_INCREMENT, or SERIAL column, or you have defined a SEQUENCE/GENERATOR, you can use the element in an statement to use or return that database-generated