Introduction 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With the client end connecting directly to the kinds of ORM frameworks. 1 Apache ShardingSphere document, v5.0.0-beta • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC. • XA will not invade the applications. Seata BASE transaction Seata is a distributed transaction framework developed by Alibaba Group and Ant Finance. The goal of AT transaction is to provide incremental

document, v5.0.0 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer. With the client end connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC. • predecessor of Apache ShardingSphere, ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With the client end con‐ necting directly to the

instead of the database itself. ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. 1 Apache ShardingSphere document, v5 native environment. Independent ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. With the client connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template, or direct use of JDBC; •

document, v5.1.1 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer. With the client end connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC; • predecessor of Apache ShardingSphere, ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With the client end con‐ necting directly to the

instead of the database itself. 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. 1.1.2 ShardingSphere-Proxy ShardingSphere‐Proxy native environment. 3.1 Using ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. With the client connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template, or direct use of JDBC; •

instead of the database itself. ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. ShardingSphere-Proxy ShardingSphere‐Proxy native environment. 1.3.1 Using ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. With the client connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template, or direct use of JDBC; •

document, v5.1.2 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer. With the client end connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC; • predecessor of Apache ShardingSphere, ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With the client end con‐ necting directly to the

instead of the database itself. 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. 1.1.2 ShardingSphere-Proxy ShardingSphere‐Proxy native environment. 3.1 Using ShardingSphere-JDBC ShardingSphere‐JDBC is a lightweight Java framework that provides additional services at Java’s JDBC layer. With the client connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template, or direct use of JDBC; •

ShardingSphere 的 XA 分布式事务尚未在 Spring Boot OSS 3 上就绪，此限制同样适用于其他基于 Jakarta EE 9+ 的 Web Framework，如 Quarkus 3，Micronaut Framework 4 和 Helidon 3。 用户仅需要配置如下。 org LONGBLOB NOT NULL COMMENT 'rollback info', `log_status` INT(11) NOT NULL COMMENT '0:normal status,1:defense status ', `log_created` DATETIME(6) NOT NULL COMMENT 'create datetime', `log_modified` DATETIME(6) document 3. 在函数上使用 Jakarta EE 9/10 的 jakarta.transaction.Transactional 注解，这是被允许 的。 4. 在函数上使用 Spring Framework 的 org.springframework.transaction.annotation. Transactional 注解，这是被允许的。 5. 在函数上使用 io.seata.spring

ShardingSphere 的 XA 分布式事务尚未在 Spring Boot OSS 3 上就绪，此限制同样适用于其他基于 Jakarta EE 9+ 的 Web Framework，如 Quarkus 3，Micronaut Framework 4 和 Helidon 3。 用户仅需要配置如下。 org LONGBLOB NOT NULL COMMENT 'rollback info', `log_status` INT(11) NOT NULL COMMENT '0:normal status,1:defense status', `log_created` DATETIME NOT NULL COMMENT 'create datetime', `log_modified` DATETIME NOT