This is an automated email from the ASF dual-hosted git repository.

kangkaisen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-doris.git


The following commit(s) were added to refs/heads/master by this push:
     new 54da5a4  Fix delete statement doc display not correctly (#3445)
54da5a4 is described below

commit 54da5a491c755b0cf07d336e6b788da3119136ee
Author: yangzhg <780531...@qq.com>
AuthorDate: Fri May 1 19:20:00 2020 +0800

    Fix delete statement doc display not correctly (#3445)
---
 .../sql-statements/Data Manipulation/DELETE.md     | 64 +++++++++++-----------
 1 file changed, 32 insertions(+), 32 deletions(-)

diff --git a/docs/en/sql-reference/sql-statements/Data Manipulation/DELETE.md 
b/docs/en/sql-reference/sql-statements/Data Manipulation/DELETE.md
index 42ae302..c586d20 100644
--- a/docs/en/sql-reference/sql-statements/Data Manipulation/DELETE.md  
+++ b/docs/en/sql-reference/sql-statements/Data Manipulation/DELETE.md  
@@ -25,38 +25,38 @@ under the License.
 -->
 
 # DELETE
-Description
-
-This statement is used to conditionally delete data in the specified table 
(base index) partition.
-This action deletes the rollup index data associated with this base index at 
the same time.
-Grammar:
-PART FROM table name [PARTITION partition name]
-WHERE
-column_name1 op value[ AND column_name2 op value ...];
-
-Explain:
-1) Optional types of OP include: =,>,<,>=,<=,<=,<=,!=
-2) Conditions on key columns can only be specified.
-2) When the selected key column does not exist in a rollup, delete cannot be 
performed.
-3) The relationship between conditions can only be "and".
-If you want to achieve the "or" relationship, you need to divide the 
conditions into two DELETE statements.
-4) If you partition a table for RANGE, you must specify PARTITION. If it is a 
single partition table, you can not specify it.
-
-Be careful:
-This statement may reduce query efficiency for a period of time after 
execution.
-The degree of impact depends on the number of deletion conditions specified in 
the statement.
-The more conditions specified, the greater the impact.
-
-'35;'35; example
-
-1. Delete rows whose K1 column value is 3 in my_table partition p 1
-DELETE FROM my_table PARTITION p1
-WHERE k1 = 3;
-
-2. Delete rows whose K1 column value is greater than or equal to 3 and whose 
K2 column value is "abc" in my_table partition P1
-DELETE FROM my_table PARTITION p1
-WHERE k1 >= 3 AND k2 = "abc";
+## Description
+
+    This statement is used to conditionally delete data in the specified table 
(base index) partition.
+    This action deletes the rollup index data associated with this base index 
at the same time.
+    Grammar:
+        DELETE FROM table name [PARTITION partition name]
+        WHERE
+        column_name1 op value[ AND column_name2 op value ...];
+    
+    Explain:
+        1) Optional types of OP include: =,>,<,>=,<=,<=,<=,!=
+        2) Conditions on key columns can only be specified.
+        2) When the selected key column does not exist in a rollup, delete 
cannot be performed.
+        3) The relationship between conditions can only be "and".
+        If you want to achieve the "or" relationship, you need to divide the 
conditions into two DELETE statements.
+        4) If you partition a table for RANGE, you must specify PARTITION. If 
it is a single partition table, you can not specify it.
+    
+    Notice:
+        This statement may reduce query efficiency for a period of time after 
execution.
+        The degree of impact depends on the number of deletion conditions 
specified in the statement.
+        The more conditions specified, the greater the impact.
+
+## example
+
+    1. Delete rows whose K1 column value is 3 in my_table partition p 1
+    DELETE FROM my_table PARTITION p1
+    WHERE k1 = 3;
+    
+    2. Delete rows whose K1 column value is greater than or equal to 3 and 
whose K2 column value is "abc" in my_table partition P1
+    DELETE FROM my_table PARTITION p1
+    WHERE k1 >= 3 AND k2 = "abc";
 
 ## keyword
-DELETE
+    DELETE
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to