RaigorJiang opened a new issue #10986: URL: https://github.com/apache/shardingsphere/issues/10986
Hi community, This issue is for [#10887](https://github.com/apache/shardingsphere/issues/10887). ### Background Refor to #10972 ### Aim Optimize change history of ShardingSphere-JDBC Spring Namespace Configuration. (Chinese version). ### How to 1. Migrate `Spring Namespace Configuration` change history from `4.1.2.Configuration Manual`->`Spring Namespace Configuration`->`Change History` to `7.2.API Change History`->`7.2.1.ShardingSphere-JDBC`->`Spring Namespace Configuration`; 2. Refer to the documents of each version on the official website, check whether the change history is correct, and fill in the missing parts. 3. The content organization of the change history is as follows: - ShardingSphere-5.0.0-beta - Sharding - Readwrite-splitting - Encryption - Shadow DB - Governance - ShardingSphere-4.x - Sharding - Readwrite-splitting - Data Masking - Orchestration - ShardingSphere-3.x - Sharding - Readwrite-splitting - Orchestration - ShardingSphere-2.x - Sharding - Readwrite-splitting - Orchestration ### Reference - [Apache ShardingSphere website](https://shardingsphere.apache.org/) - [Spring Namespace Configuration change history](https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/configuration/spring-namespace/change-history/) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
