operations. 8.6.7 Limitations Procedures Supported • Migration of peripheral data to databases managed by Apache ShardingSphere. • Target proxy without rule or configure any rule. • Migration of single Sharding Single Table Background Single rule is used to specify which single tables need to be managed by ShardingSphere, or to set the default single table data source. 9.1. ShardingSphere-JDBC 84 Sharding Single Table Background Single rule is used to specify which single tables need to be managed by ShardingSphere, or to set the default single table data source. Parameters Class：org.apache

operations. 3.7.7 Limitations Procedures Supported • Migration of peripheral data to databases managed by Apache ShardingSphere. • Migration of integer or string unique key tables. • Migration of integer additional YAML files, and the logical databases are managed through DistSQL. ‐ Editing permissions for files are no longer required, and configuration is managed through DistSQL. ‐ Configuration changes take ithmType [, PROPERTIES([algorithmProperties])]) • RESOURCES needs to use data source resources managed by RDL • shardingAlgorithmType specifies the type of automatic sharding algorithm, please refer

"default_environment _name"> MANAGED If we use the transaction manager of type JDBC, the application is responsible for the transaction management operations, such as, commit, roll-back, etc... If we use the transaction manager of type MANAGED, the application server is responsible to manage the connection life cycle. It is generally used

operations. 3.7.7 Limitations Procedures Supported • Migration of peripheral data to databases managed by Apache ShardingSphere. • Migration of integer or string primary key tables. Procedures not supported additional YAML files, and the logical databases are managed through DistSQL. ‐ Editing permissions for files are no longer required, and configuration is managed through DistSQL. ‐ Configuration changes take keyGeneratorDefinition: keyGeneratorName (algorithmDefinition) • RESOURCES needs to use data source resources managed by RDL • shardingAlgorithmType specifies the type of automatic sharding algorithm, please refer

operations. 8.6.7 Limitations Procedures Supported • Migration of peripheral data to databases managed by Apache ShardingSphere. • Target proxy without rule or configure any rule. • Migration of single Sharding Single Table Background Single rule is used to specify which single tables need to be managed by ShardingSphere, or to set the default single table data source. Parameters rules: - !SINGLE additional YAML files, and the logical databases are managed through DistSQL. ‐ Editing permissions for files are no longer required, and configuration is managed 9.2. ShardingSphere-Proxy 166 Apache ShardingSphere

MyBatis 中有两种类型的事务管理器（也就是 type=”[JDBC|MANAGED]”）： Save web pages as PDF manually or automatically with PDFmyURL JDBC – 这个配置就是直接使用了 JDBC 的提交和回滚设置，它依赖于从数据源得到的连接来管理事务范围。 MANAGED – 这个配置几乎没做什么。它从来不提交或回滚一个连接，而是让容器来管理事务的整个生命周期（比如 默认情况下它会关闭连接，然而一些容器并不希望这样，因此需要将 closeConnection 属性设置为 false 来阻止它默 认的关闭行为。例如: NOTE NOTE 如果你正在使用 Spring type="POOLED"> ... ... ... 如果你调用了

5) transactionManager type： JDBC | MANAGED | 自定义 JDBC：使用了 JDBC 的提交和回滚设置，依赖于从数据源得到的连接来管理事务 范 围。 JdbcTransactionFactory MANAGED：不提交或回滚一个连接、让容器来管理事务的整个生命周期（比如 JEE 应用服务器的上下文）。 ManagedTransactionFactory

the SQL execution is abnormal, and run Commit, and data remains con‐ sistent. XA Transaction managed by XA Statement • When using XA START to open a XA Transaction, ShardingSphere will pass it to backend application during scaling job. 4.7.6 User Norms Supported • Migrate data outside into databases which managed by Apache ShardingSphere; • Scale out data between data nodes of Apache ShardingSphere. 4.7. Scaling keyGeneratorDefinition: keyGeneratorName (algorithmDefinition) • RESOURCES needs to use data source resources managed by RDL • shardingAlgorithmType specifies the type of automatic sharding algorithm, please refer

the SQL execution is abnormal, and run Commit, and data re‐ mains consistent. XA Transaction managed by XA Statement • When using XA START to open a XA Transaction, ShardingSphere will pass it to backend application during scaling job. 4.7.6 User Norms Supported • Migrate data outside into databases which managed by Apache ShardingSphere; • Scale out data between data nodes of Apache ShardingSphere. 4.7. Scaling keyGeneratorDefinition: keyGeneratorName (algorithmDefinition) • RESOURCES needs to use data source resources managed by RDL • shardingAlgorithmType specifies the type of automatic sharding algorithm, please refer

ShardingSphere document, v5.0.0 4.6.6 User Norms Supported • Migrate data outside into databases which managed by Apache ShardingSphere; • Scale out data between data nodes of Apache ShardingSphere. Unsupported document, v5.0.0 algorithmProperty: key=value • RESOURCES needs to use data source resources managed by RDL • shardingAlgorithmType specifies the type of automatic sharding algorithm, please refer mapping relationship between the source database and the shadow library. You need to use the resource managed by RDL, please refer to resource • shadowAlgorithm can act on multiple shadowTableRule at the same