This is an automated email from the ASF dual-hosted git repository.
menghaoran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new 1e01806 Update en summary for mix rule configuration (#9288)
1e01806 is described below
commit 1e018065a3827b482b7117067c96bafc5d85db87
Author: Liang Zhang <[email protected]>
AuthorDate: Wed Feb 3 13:51:37 2021 +0800
Update en summary for mix rule configuration (#9288)
---
.../user-manual/shardingsphere-jdbc/configuration/_index.en.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git
a/docs/document/content/user-manual/shardingsphere-jdbc/configuration/_index.en.md
b/docs/document/content/user-manual/shardingsphere-jdbc/configuration/_index.en.md
index 880d2fb..e6d4c6d 100644
---
a/docs/document/content/user-manual/shardingsphere-jdbc/configuration/_index.en.md
+++
b/docs/document/content/user-manual/shardingsphere-jdbc/configuration/_index.en.md
@@ -12,3 +12,9 @@ This chapter is a configuration manual for
ShardingSphere-JDBC, which can also b
ShardingSphere-JDBC has provided 4 kinds of configuration methods for
different situations.
By configuration, application developers can flexibly use data sharding,
replica query, data encryption, shadow database or the combination of them.
+
+Mixed rule configurations are very similar to single rule configuration,
except for the differences from single rule to multiple rules.
+
+It should be noted that the superposition between rules are data source and
table name related.
+If the previous rule is data source oriented aggregation, the next rule needs
to use the aggregated logical data source name configured by the previous rule
when configuring the data source;
+Similarly, if the previous rule is table oriented aggregation, the next rule
needs to use the aggregated logical table name configured by the previous rule
when configuring the table.
