databases in the same log . . . . . . . . . . . . . . . . . . . . . . 215 To distinguish databases and users in the same log . . . . . . . . . . . . . . . . . 216 To split into different log files . . . . yaml or properties leading incorrect result when loading Oracle metadata？ . . . . . . 369 7.9 API Change Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 7.9.1 ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Spring namespace configuration change history . . . . . . . . . . . . . . . . . . 412 Spring Boot Starter Configuration . . . . . . .

when integrating ShardingSphere with Spring Boot 2.x ? . . . . . . . . . . . . . . . . 356 7.9 API Change Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 7.9.1 ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Spring namespace configuration change history . . . . . . . . . . . . . . . . . . 399 Spring Boot Starter Configuration . . . . . . . c-core ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 2.1.2 Rules Configuration ShardingSphere‐JDBC

. . 50 Third‐party Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4.5.5 Observability 7.26 26. [Other] Why is the database sharding result not correct when using Proxool?312 7.8 API Change Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 7.8.1 ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Spring namespace configuration change history . . . . . . . . . . . . . . . . . . 352 Spring Boot Starter Configuration . . . . . . .

ShardingSphere document, v5.2.0 ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 3. Edit application.yml. spring: shardingsphere: transactions after sharding; • Support RC isolation level; • Rollback transaction according to undo log; • Support recovery committing transaction automatically after the service is down. Unsupported Type Apache ShardingSphere does not provide database high availability capability. It senses the change of databases’primary‐secondary relationship through a third‐party provided high availability solu‐

ShardingSphere document, v5.2.1 ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 3. Edit application.yml. spring: shardingsphere: Supported • Support cross‐database transactions after sharding; • Rollback transaction according to undo log; • Support recovery committing transaction automatically after the service is down. Unsupported Type Apache ShardingSphere does not provide database high availability capability. It senses the change of databases’primary‐secondary relationship through a third‐party provided high availability solu‐

. . 70 Third‐party Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.4.5 Observability c-core ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 2.1.2 2. Rules Configuration ShardingSphere‐JDBC the SQL that runs rightly in single‐node databases may not be right in the sharding database. The change of table name after sharding, or misconducts caused by operations such as pagination, order by or

${latest.release.version} 14 Apache ShardingSphere document Notice: Please change ${latest.release.version} to the actual version. 3. Create YAML configuration file # JDBC database statistical indicators are collected through probes for display by third‐party applications. Logging The log can be easily expanded through the agent to provide more information for analyzing the system running e-jdbc ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. Sample Standalone Mode ModeConfiguration modeConfig

${latest.release.version} 14 Apache ShardingSphere document Notice: Please change ${latest.release.version} to the actual version. 3. Create YAML configuration file # JDBC database statistical indicators are collected through probes for display by third‐party applications. Logging The log can be easily expanded through the agent to provide more information for analyzing the system running c-core ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 9.1. ShardingSphere-JDBC 93 Apache ShardingSphere

6.3.4 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Log in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Login with misfire to re‐execute. 5.5 Job Open Ecosystem Flexible customized jobs is the most important design change in ElasticJob 3.x . The new version is based on the design concept of the Apache ShardingSphere RequestMethod.POST) public void execute(String source, @RequestHeader String shardingContext) { log.info("execute from source : {}, shardingContext : {}", source, shardingContext); } } 6.1. Usage

指定 MyBatis 增加 到日志名称的前 缀。 Any String Not set logImpl 指定 MyBatis 所用 日志的具体实现， 未指定时将自动查 SLF4J | LOG4J | LOG4J2 | JDK_LOGGING | Not set Save web pages as PDF manually or automatically with PDFmyURL 未指定时将自动查 least one of the columns mapped to the child's properties is non null. With this attribute you can change this behaviour by specifiying which columns must have a value so MyBatis will create a child object 项目信息 项目信息 项目报表 项目报表 Logging Mybatis内置的日志工厂提供日志功能，具体的日志实现有以下几种工具： SLF4J Apache Commons Logging Log4j 2 Log4j JDK logging 具体选择哪个日志实现工具由MyBatis的内置日志工厂确定。它会使用最先找到的（按上文列举的顺序查找）。 如果一个都未找到，日 志功能就会被禁用。 不少应用