You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by pa...@apache.org on 2020/07/04 01:18:31 UTC
[shardingsphere] branch master updated: fix #4913 change image
chinese to eng (#6262)
This is an automated email from the ASF dual-hosted git repository.
panjuan 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 a43b7c8 fix #4913 change image chinese to eng (#6262)
a43b7c8 is described below
commit a43b7c8c75a3348505074f3b4a6ad675e15aee54
Author: xbkaishui <xb...@126.com>
AuthorDate: Sat Jul 4 09:18:08 2020 +0800
fix #4913 change image chinese to eng (#6262)
---
.../content/features/sharding/principle/rewrite.en.md | 4 ++--
.../static/img/sharding/pagination_with_rewrite_en.png | Bin 0 -> 72839 bytes
.../img/sharding/pagination_without_rewrite_en.png | Bin 0 -> 46006 bytes
3 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/document/content/features/sharding/principle/rewrite.en.md b/docs/document/content/features/sharding/principle/rewrite.en.md
index fe6406e..9c91a21 100644
--- a/docs/document/content/features/sharding/principle/rewrite.en.md
+++ b/docs/document/content/features/sharding/principle/rewrite.en.md
@@ -163,7 +163,7 @@ SELECT score FROM t_score ORDER BY score DESC LIMIT 1, 2;
The following picture shows the pagination execution results without SQL rewrite.
-
+
As shown in the picture, if you want to acquire the second and the third piece of data ordered by score common in both tables, and they are supposed to be `95` and `90`.
Since the executed SQL can only acquire the second and the third piece of data from each table, i.e., `90` and `80` from t_score_0, `85` and `75` from t_score_1.
@@ -172,7 +172,7 @@ When merging results, it can only merge from `90`, `80`, `85` and `75` already a
The right way is to rewrite pagination conditions as `LIMIT 0, 3`, take out all the data from the first two pages and combine sorting conditions to calculate the right data.
The following picture shows the execution of pagination results after SQL rewrite.
-
+
The latter the offset position is, the lower the efficiency of using LIMIT pagination will be.
There are many ways to avoid using LIMIT as pagination method, such as constructing a secondary index to record line record number and line offset amount,
diff --git a/docs/document/static/img/sharding/pagination_with_rewrite_en.png b/docs/document/static/img/sharding/pagination_with_rewrite_en.png
new file mode 100644
index 0000000..d556454
Binary files /dev/null and b/docs/document/static/img/sharding/pagination_with_rewrite_en.png differ
diff --git a/docs/document/static/img/sharding/pagination_without_rewrite_en.png b/docs/document/static/img/sharding/pagination_without_rewrite_en.png
new file mode 100644
index 0000000..4f1ef75
Binary files /dev/null and b/docs/document/static/img/sharding/pagination_without_rewrite_en.png differ