From 4b09a03a516122ac47cc118eaa04620074afc54f Mon Sep 17 00:00:00 2001 From: "Ru, Li Yi" Date: Thu, 11 Apr 2024 11:39:26 +0000 Subject: [PATCH] ddm_umn Reviewed-by: Wagner, Fabian Co-authored-by: Ru, Li Yi Co-committed-by: Ru, Li Yi --- docs/ddm/umn/ALL_META.TXT.json | 138 +++++++++--------- docs/ddm/umn/CLASS.TXT.json | 70 ++++----- docs/ddm/umn/ddm-08-0004.html | 31 ---- docs/ddm/umn/ddm-08-0008.html | 16 -- docs/ddm/umn/ddm-08-0009.html | 17 --- docs/ddm/umn/ddm-08-0013.html | 16 -- docs/ddm/umn/ddm-08-0015.html | 32 ---- docs/ddm/umn/ddm-08-0017.html | 20 --- docs/ddm/umn/ddm-08-0021.html | 22 --- docs/ddm/umn/ddm-08-0022.html | 21 --- docs/ddm/umn/ddm-08-0024.html | 16 -- docs/ddm/umn/ddm-08-0025.html | 21 --- docs/ddm/umn/ddm-08-0026.html | 16 -- docs/ddm/umn/ddm-08-0029.html | 18 --- docs/ddm/umn/ddm_01_0000.html | 4 +- .../{ddm-01-0002.html => ddm_01_0002.html} | 10 +- .../{ddm-01-0003.html => ddm_01_0003.html} | 4 +- .../{ddm-01-0004.html => ddm_01_0004.html} | 8 +- docs/ddm/umn/ddm_01_0005.html | 2 +- docs/ddm/umn/ddm_01_0174.html | 2 +- docs/ddm/umn/ddm_01_0175.html | 2 +- docs/ddm/umn/ddm_03_0030.html | 2 +- docs/ddm/umn/ddm_03_0031.html | 2 +- docs/ddm/umn/ddm_03_0032.html | 2 +- docs/ddm/umn/ddm_03_0034.html | 2 +- docs/ddm/umn/ddm_03_0035.html | 2 +- docs/ddm/umn/ddm_03_0038.html | 2 +- docs/ddm/umn/ddm_03_0039.html | 2 +- docs/ddm/umn/ddm_03_0040.html | 2 +- docs/ddm/umn/ddm_03_0053.html | 4 +- docs/ddm/umn/ddm_03_0062.html | 2 +- docs/ddm/umn/ddm_03_0063.html | 2 +- docs/ddm/umn/ddm_03_0067.html | 4 +- docs/ddm/umn/ddm_03_0068.html | 2 +- docs/ddm/umn/ddm_03_0069.html | 2 +- docs/ddm/umn/ddm_03_0070.html | 2 +- docs/ddm/umn/ddm_03_0071.html | 2 +- .../{ddm_03_0064.html => ddm_03_0131.html} | 2 +- docs/ddm/umn/ddm_04_0009.html | 2 +- docs/ddm/umn/ddm_05_0001.html | 4 +- docs/ddm/umn/ddm_05_0003.html | 15 -- docs/ddm/umn/ddm_05_0004.html | 16 -- docs/ddm/umn/ddm_05_0133.html | 15 ++ docs/ddm/umn/ddm_05_0134.html | 16 ++ docs/ddm/umn/ddm_0600017.html | 72 --------- docs/ddm/umn/ddm_06_0001.html | 2 +- docs/ddm/umn/ddm_06_00017.html | 94 ------------ .../{ddm_0600016.html => ddm_06_0016.html} | 40 ++--- docs/ddm/umn/ddm_06_0017.html | 73 +++++++++ docs/ddm/umn/ddm_06_0132.html | 94 ++++++++++++ .../{ddm-08-0001.html => ddm_08_0001.html} | 10 +- .../{ddm-08-0002.html => ddm_08_0002.html} | 16 +- .../{ddm-08-0003.html => ddm_08_0003.html} | 4 +- docs/ddm/umn/ddm_08_0004.html | 31 ++++ .../{ddm-08-0005.html => ddm_08_0005.html} | 12 +- .../{ddm-08-0006.html => ddm_08_0006.html} | 42 +++--- .../{ddm-08-0007.html => ddm_08_0007.html} | 12 +- docs/ddm/umn/ddm_08_0008.html | 16 ++ docs/ddm/umn/ddm_08_0009.html | 17 +++ .../{ddm-08-0010.html => ddm_08_0010.html} | 28 ++-- .../{ddm-08-0011.html => ddm_08_0011.html} | 10 +- .../{ddm-08-0012.html => ddm_08_0012.html} | 36 ++--- docs/ddm/umn/ddm_08_0013.html | 16 ++ .../{ddm-08-0014.html => ddm_08_0014.html} | 8 +- docs/ddm/umn/ddm_08_0015.html | 32 ++++ docs/ddm/umn/ddm_08_0017.html | 20 +++ docs/ddm/umn/ddm_08_0021.html | 22 +++ docs/ddm/umn/ddm_08_0022.html | 21 +++ .../{ddm-08-0023.html => ddm_08_0023.html} | 10 +- docs/ddm/umn/ddm_08_0024.html | 16 ++ docs/ddm/umn/ddm_08_0025.html | 21 +++ docs/ddm/umn/ddm_08_0026.html | 16 ++ .../{ddm-08-0027.html => ddm_08_0027.html} | 16 +- docs/ddm/umn/ddm_08_0029.html | 2 +- docs/ddm/umn/ddm_08_0032.html | 2 +- docs/ddm/umn/ddm_08_0130.html | 18 +++ docs/ddm/umn/ddm_10_0018.html | 2 +- docs/ddm/umn/ddm_12_0006.html | 2 +- docs/ddm/umn/ddm_12_0100.html | 2 +- docs/ddm/umn/ddm_history_0003.html | 39 +++++ docs/ddm/umn/ddm_histroy_0003.html | 34 ----- 81 files changed, 753 insertions(+), 747 deletions(-) delete mode 100644 docs/ddm/umn/ddm-08-0004.html delete mode 100644 docs/ddm/umn/ddm-08-0008.html delete mode 100644 docs/ddm/umn/ddm-08-0009.html delete mode 100644 docs/ddm/umn/ddm-08-0013.html delete mode 100644 docs/ddm/umn/ddm-08-0015.html delete mode 100644 docs/ddm/umn/ddm-08-0017.html delete mode 100644 docs/ddm/umn/ddm-08-0021.html delete mode 100644 docs/ddm/umn/ddm-08-0022.html delete mode 100644 docs/ddm/umn/ddm-08-0024.html delete mode 100644 docs/ddm/umn/ddm-08-0025.html delete mode 100644 docs/ddm/umn/ddm-08-0026.html delete mode 100644 docs/ddm/umn/ddm-08-0029.html rename docs/ddm/umn/{ddm-01-0002.html => ddm_01_0002.html} (72%) rename docs/ddm/umn/{ddm-01-0003.html => ddm_01_0003.html} (84%) rename docs/ddm/umn/{ddm-01-0004.html => ddm_01_0004.html} (59%) rename docs/ddm/umn/{ddm_03_0064.html => ddm_03_0131.html} (90%) delete mode 100644 docs/ddm/umn/ddm_05_0003.html delete mode 100644 docs/ddm/umn/ddm_05_0004.html create mode 100644 docs/ddm/umn/ddm_05_0133.html create mode 100644 docs/ddm/umn/ddm_05_0134.html delete mode 100644 docs/ddm/umn/ddm_0600017.html delete mode 100644 docs/ddm/umn/ddm_06_00017.html rename docs/ddm/umn/{ddm_0600016.html => ddm_06_0016.html} (55%) create mode 100644 docs/ddm/umn/ddm_06_0017.html create mode 100644 docs/ddm/umn/ddm_06_0132.html rename docs/ddm/umn/{ddm-08-0001.html => ddm_08_0001.html} (70%) rename docs/ddm/umn/{ddm-08-0002.html => ddm_08_0002.html} (68%) rename docs/ddm/umn/{ddm-08-0003.html => ddm_08_0003.html} (86%) create mode 100644 docs/ddm/umn/ddm_08_0004.html rename docs/ddm/umn/{ddm-08-0005.html => ddm_08_0005.html} (53%) rename docs/ddm/umn/{ddm-08-0006.html => ddm_08_0006.html} (54%) rename docs/ddm/umn/{ddm-08-0007.html => ddm_08_0007.html} (50%) create mode 100644 docs/ddm/umn/ddm_08_0008.html create mode 100644 docs/ddm/umn/ddm_08_0009.html rename docs/ddm/umn/{ddm-08-0010.html => ddm_08_0010.html} (51%) rename docs/ddm/umn/{ddm-08-0011.html => ddm_08_0011.html} (57%) rename docs/ddm/umn/{ddm-08-0012.html => ddm_08_0012.html} (56%) create mode 100644 docs/ddm/umn/ddm_08_0013.html rename docs/ddm/umn/{ddm-08-0014.html => ddm_08_0014.html} (62%) create mode 100644 docs/ddm/umn/ddm_08_0015.html create mode 100644 docs/ddm/umn/ddm_08_0017.html create mode 100644 docs/ddm/umn/ddm_08_0021.html create mode 100644 docs/ddm/umn/ddm_08_0022.html rename docs/ddm/umn/{ddm-08-0023.html => ddm_08_0023.html} (50%) create mode 100644 docs/ddm/umn/ddm_08_0024.html create mode 100644 docs/ddm/umn/ddm_08_0025.html create mode 100644 docs/ddm/umn/ddm_08_0026.html rename docs/ddm/umn/{ddm-08-0027.html => ddm_08_0027.html} (51%) create mode 100644 docs/ddm/umn/ddm_08_0130.html create mode 100644 docs/ddm/umn/ddm_history_0003.html delete mode 100644 docs/ddm/umn/ddm_histroy_0003.html diff --git a/docs/ddm/umn/ALL_META.TXT.json b/docs/ddm/umn/ALL_META.TXT.json index 7eac736d..0c828333 100644 --- a/docs/ddm/umn/ALL_META.TXT.json +++ b/docs/ddm/umn/ALL_META.TXT.json @@ -93,8 +93,8 @@ "githuburl":"" }, { - "uri":"ddm-01-0003.html", - "node_id":"ddm-01-0003.xml", + "uri":"ddm_01_0003.html", + "node_id":"ddm_01_0003.xml", "product_code":"ddm", "code":"6", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -111,8 +111,8 @@ "githuburl":"" }, { - "uri":"ddm-01-0004.html", - "node_id":"ddm-01-0004.xml", + "uri":"ddm_01_0004.html", + "node_id":"ddm_01_0004.xml", "product_code":"ddm", "code":"7", "des":"Restrictions on network access are as follows:The data nodes and ECSs running your applications must be in the same VPC as your DDM instance.To access DDM from your compu", @@ -201,8 +201,8 @@ "githuburl":"" }, { - "uri":"ddm-01-0002.html", - "node_id":"ddm-01-0002.xml", + "uri":"ddm_01_0002.html", + "node_id":"ddm_01_0002.xml", "product_code":"ddm", "code":"12", "des":"As an OLTP-oriented service, DDM allows you to access distributed relational databases across a variety of industries.", @@ -399,8 +399,8 @@ "githuburl":"" }, { - "uri":"ddm_06_00017.html", - "node_id":"ddm_06_00017.xml", + "uri":"ddm_06_0132.html", + "node_id":"ddm_06_0132.xml", "product_code":"ddm", "code":"23", "des":"You have logged in to the DDM console.", @@ -1029,8 +1029,8 @@ "githuburl":"" }, { - "uri":"ddm_03_0064.html", - "node_id":"ddm_03_0064.xml", + "uri":"ddm_03_0131.html", + "node_id":"ddm_03_0131.xml", "product_code":"ddm", "code":"58", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1263,8 +1263,8 @@ "githuburl":"" }, { - "uri":"ddm_05_0003.html", - "node_id":"ddm_05_0003.xml", + "uri":"ddm_05_0133.html", + "node_id":"ddm_05_0133.xml", "product_code":"ddm", "code":"71", "des":"You have logged in to the DDM console.", @@ -1281,8 +1281,8 @@ "githuburl":"" }, { - "uri":"ddm_05_0004.html", - "node_id":"ddm_05_0004.xml", + "uri":"ddm_05_0134.html", + "node_id":"ddm_05_0134.xml", "product_code":"ddm", "code":"72", "des":"You have logged in to the DDM console.Deleted accounts cannot be recovered. Exercise caution when performing this operation.", @@ -1335,8 +1335,8 @@ "githuburl":"" }, { - "uri":"ddm_0600016.html", - "node_id":"ddm_0600016.xml", + "uri":"ddm_06_0016.html", + "node_id":"ddm_06_0016.xml", "product_code":"ddm", "code":"75", "des":"DDM allows you to restore data from the current instance to any point in time using an existing backup. This is a good choice for routine service backup and restoration.T", @@ -1353,8 +1353,8 @@ "githuburl":"" }, { - "uri":"ddm_0600017.html", - "node_id":"ddm_0600017.xml", + "uri":"ddm_06_0017.html", + "node_id":"ddm_06_0017.xml", "product_code":"ddm", "code":"76", "des":"DDM automatically backs up DDM instance metadata at 02:00 UTC+00:00 every day and retains the backup data for 30 days. Metadata backup is also triggered by key operations", @@ -1587,8 +1587,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0001.html", - "node_id":"ddm-08-0001.xml", + "uri":"ddm_08_0001.html", + "node_id":"ddm_08_0001.xml", "product_code":"ddm", "code":"89", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1623,8 +1623,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0003.html", - "node_id":"ddm-08-0003.xml", + "uri":"ddm_08_0003.html", + "node_id":"ddm_08_0003.xml", "product_code":"ddm", "code":"91", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1929,8 +1929,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0004.html", - "node_id":"ddm-08-0004.xml", + "uri":"ddm_08_0004.html", + "node_id":"ddm_08_0004.xml", "product_code":"ddm", "code":"108", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1947,8 +1947,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0005.html", - "node_id":"ddm-08-0005.xml", + "uri":"ddm_08_0005.html", + "node_id":"ddm_08_0005.xml", "product_code":"ddm", "code":"109", "des":"INSERT is used to insert data into database objects.INSERT DELAYED is not supported.Only INSERT statements that contain sharding fields are supported.PARTITION syntax is ", @@ -1965,8 +1965,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0007.html", - "node_id":"ddm-08-0007.xml", + "uri":"ddm_08_0007.html", + "node_id":"ddm_08_0007.xml", "product_code":"ddm", "code":"110", "des":"REPLACE is used to insert rows into or replace rows in a table.PARTITION syntax is not supported.If an auto-increment table has no ID, you can insert a data record with a", @@ -1983,8 +1983,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0008.html", - "node_id":"ddm-08-0008.xml", + "uri":"ddm_08_0008.html", + "node_id":"ddm_08_0008.xml", "product_code":"ddm", "code":"111", "des":"DELETE is used to delete rows that meet conditions from a table.The WHERE clause does not support subqueries, including correlated and non-correlated subqueries.Data in r", @@ -2001,8 +2001,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0009.html", - "node_id":"ddm-08-0009.xml", + "uri":"ddm_08_0009.html", + "node_id":"ddm_08_0009.xml", "product_code":"ddm", "code":"112", "des":"Subqueries are not supported, including correlated and non-correlated subqueries.Cross-shard subquery is not supported.The WHERE condition in the UPDATE statement does no", @@ -2019,8 +2019,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0006.html", - "node_id":"ddm-08-0006.xml", + "uri":"ddm_08_0006.html", + "node_id":"ddm_08_0006.xml", "product_code":"ddm", "code":"113", "des":"SELECT is generally used to query data in one or more tables.Supported syntaxSyntaxDescriptionselect_exprIndicates a column that you want to query.FROM table_referencesIn", @@ -2037,8 +2037,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0010.html", - "node_id":"ddm-08-0010.xml", + "uri":"ddm_08_0010.html", + "node_id":"ddm_08_0010.xml", "product_code":"ddm", "code":"114", "des":"table_references:table_reference:table_factor:join_table:join_condition:SELECT STRAIGHT_JOIN and NATURAL JOIN are not supported.", @@ -2055,8 +2055,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0011.html", - "node_id":"ddm-08-0011.xml", + "uri":"ddm_08_0011.html", + "node_id":"ddm_08_0011.xml", "product_code":"ddm", "code":"115", "des":"SELECT statements in UNION do not support duplicate column names.", @@ -2073,8 +2073,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0012.html", - "node_id":"ddm-08-0012.xml", + "uri":"ddm_08_0012.html", + "node_id":"ddm_08_0012.xml", "product_code":"ddm", "code":"116", "des":"ExampleSyntaxExampleSyntaxExampleSyntaxExampleEach derived table must have an alias.A derived table cannot be a correlated subquery.In some cases, correct results cannot ", @@ -2127,8 +2127,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0013.html", - "node_id":"ddm-08-0013.xml", + "uri":"ddm_08_0013.html", + "node_id":"ddm_08_0013.xml", "product_code":"ddm", "code":"119", "des":"DDM is compatible with the MySQL license and syntax, but the use of SQL statements is limited due to differences between distributed databases and single-node databases.T", @@ -2145,8 +2145,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0002.html", - "node_id":"ddm-08-0002.xml", + "uri":"ddm_08_0002.html", + "node_id":"ddm_08_0002.xml", "product_code":"ddm", "code":"120", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2163,8 +2163,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0014.html", - "node_id":"ddm-08-0014.xml", + "uri":"ddm_08_0014.html", + "node_id":"ddm_08_0014.xml", "product_code":"ddm", "code":"121", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2181,8 +2181,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0021.html", - "node_id":"ddm-08-0021.xml", + "uri":"ddm_08_0021.html", + "node_id":"ddm_08_0021.xml", "product_code":"ddm", "code":"122", "des":"Purpose: To check DDL consistency of all logical tables in one schemaCommand Format:Command Output:The following output is returned if DDL check results of all logical ta", @@ -2199,8 +2199,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0022.html", - "node_id":"ddm-08-0022.xml", + "uri":"ddm_08_0022.html", + "node_id":"ddm_08_0022.xml", "product_code":"ddm", "code":"123", "des":"Purpose: To check DDL consistency of physical tables in a specific logical tableCommand Format:Command Output:If the returned result set is empty, DDL results of physical", @@ -2217,8 +2217,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0015.html", - "node_id":"ddm-08-0015.xml", + "uri":"ddm_08_0015.html", + "node_id":"ddm_08_0015.xml", "product_code":"ddm", "code":"124", "des":"Command Format 1:show rule;It is used to view the sharding rule of each logical table in a certain schema.Command output:Command Format 2:show rule from;It is", @@ -2235,8 +2235,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0017.html", - "node_id":"ddm-08-0017.xml", + "uri":"ddm_08_0017.html", + "node_id":"ddm_08_0017.xml", "product_code":"ddm", "code":"125", "des":"Command Format:show topology from;It is used to view physical tables corresponding to a specified logical table.Output Details:RDS_instance_id: indicates the ", @@ -2253,8 +2253,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0029.html", - "node_id":"ddm-08-0029.xml", + "uri":"ddm_08_0130.html", + "node_id":"ddm_08_0130.xml", "product_code":"ddm", "code":"126", "des":"Command Format:show data node;It is used to view data about database shards in the RDS instance.Output Details:RDS_instance_id: indicates the ID of the RDS instance.PHYSI", @@ -2271,8 +2271,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0023.html", - "node_id":"ddm-08-0023.xml", + "uri":"ddm_08_0023.html", + "node_id":"ddm_08_0023.xml", "product_code":"ddm", "code":"127", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2289,8 +2289,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0024.html", - "node_id":"ddm-08-0024.xml", + "uri":"ddm_08_0024.html", + "node_id":"ddm_08_0024.xml", "product_code":"ddm", "code":"128", "des":"Command Format:/*+db=*/ TRUNCATE TABLEDescription:Deleting data in physical tables corresponding to in does ", @@ -2307,8 +2307,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0025.html", - "node_id":"ddm-08-0025.xml", + "uri":"ddm_08_0025.html", + "node_id":"ddm_08_0025.xml", "product_code":"ddm", "code":"129", "des":"HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way. This section describes how to use HINT syntax to delete ", @@ -2325,8 +2325,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0026.html", - "node_id":"ddm-08-0026.xml", + "uri":"ddm_08_0026.html", + "node_id":"ddm_08_0026.xml", "product_code":"ddm", "code":"130", "des":"Command Format:/*+db=,table=*/ TRUNCATE TABLEDescription:Deleting data in physical table in datab", @@ -2343,8 +2343,8 @@ "githuburl":"" }, { - "uri":"ddm-08-0027.html", - "node_id":"ddm-08-0027.xml", + "uri":"ddm_08_0027.html", + "node_id":"ddm_08_0027.xml", "product_code":"ddm", "code":"131", "des":"Command Format:/*+ allow_alter_rerun=true*/Description:Using this hint ensures that commands can be repeatedly executed, and no error is reported. This hint ", @@ -2707,7 +2707,7 @@ "node_id":"ddm_04_0009.xml", "product_code":"ddm", "code":"151", - "des":"Currently, you cannot connect to DDM using JDBC driver 5.1.46. Versions 5.1.35 to 5.1.45 are recommended.JDBC driver download address: https://dev.mysql.com/doc/index-con", + "des":"Currently, you cannot connect to DDM using JDBC driver 5.1.46. Versions 5.1.35 to 5.1.45 are recommended.JDBC driver download address:https://dev.mysql.com/downloads/conn", "doc_type":"usermanual", "kw":"JDBC driver,What Version and Parameters Should I Select?,DDM Usage,User Guide", "search_title":"", @@ -3045,8 +3045,8 @@ "githuburl":"" }, { - "uri":"ddm_histroy_0003.html", - "node_id":"ddm_histroy_0003.xml", + "uri":"ddm_history_0003.html", + "node_id":"ddm_history_0003.xml", "product_code":"ddm", "code":"170", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", diff --git a/docs/ddm/umn/CLASS.TXT.json b/docs/ddm/umn/CLASS.TXT.json index c75d604a..06fa1533 100644 --- a/docs/ddm/umn/CLASS.TXT.json +++ b/docs/ddm/umn/CLASS.TXT.json @@ -48,7 +48,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"Usage Constraints", - "uri":"ddm-01-0003.html", + "uri":"ddm_01_0003.html", "doc_type":"usermanual", "p_code":"1", "code":"6" @@ -57,7 +57,7 @@ "desc":"Restrictions on network access are as follows:The data nodes and ECSs running your applications must be in the same VPC as your DDM instance.To access DDM from your compu", "product_code":"ddm", "title":"Network Access", - "uri":"ddm-01-0004.html", + "uri":"ddm_01_0004.html", "doc_type":"usermanual", "p_code":"6", "code":"7" @@ -102,7 +102,7 @@ "desc":"As an OLTP-oriented service, DDM allows you to access distributed relational databases across a variety of industries.", "product_code":"ddm", "title":"Application Scenarios", - "uri":"ddm-01-0002.html", + "uri":"ddm_01_0002.html", "doc_type":"usermanual", "p_code":"1", "code":"12" @@ -201,7 +201,7 @@ "desc":"You have logged in to the DDM console.", "product_code":"ddm", "title":"Creating a DDM Instance", - "uri":"ddm_06_00017.html", + "uri":"ddm_06_0132.html", "doc_type":"usermanual", "p_code":"22", "code":"23" @@ -516,7 +516,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"Shard Configuration", - "uri":"ddm_03_0064.html", + "uri":"ddm_03_0131.html", "doc_type":"usermanual", "p_code":"", "code":"58" @@ -633,7 +633,7 @@ "desc":"You have logged in to the DDM console.", "product_code":"ddm", "title":"Modifying an Account", - "uri":"ddm_05_0003.html", + "uri":"ddm_05_0133.html", "doc_type":"usermanual", "p_code":"69", "code":"71" @@ -642,7 +642,7 @@ "desc":"You have logged in to the DDM console.Deleted accounts cannot be recovered. Exercise caution when performing this operation.", "product_code":"ddm", "title":"Deleting an Account", - "uri":"ddm_05_0004.html", + "uri":"ddm_05_0134.html", "doc_type":"usermanual", "p_code":"69", "code":"72" @@ -669,7 +669,7 @@ "desc":"DDM allows you to restore data from the current instance to any point in time using an existing backup. This is a good choice for routine service backup and restoration.T", "product_code":"ddm", "title":"Restoring Data to a New Instance", - "uri":"ddm_0600016.html", + "uri":"ddm_06_0016.html", "doc_type":"usermanual", "p_code":"74", "code":"75" @@ -678,7 +678,7 @@ "desc":"DDM automatically backs up DDM instance metadata at 02:00 UTC+00:00 every day and retains the backup data for 30 days. Metadata backup is also triggered by key operations", "product_code":"ddm", "title":"Restoring Metadata", - "uri":"ddm_0600017.html", + "uri":"ddm_06_0017.html", "doc_type":"usermanual", "p_code":"74", "code":"76" @@ -795,7 +795,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"SQL Syntax", - "uri":"ddm-08-0001.html", + "uri":"ddm_08_0001.html", "doc_type":"usermanual", "p_code":"", "code":"89" @@ -813,7 +813,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"DDL", - "uri":"ddm-08-0003.html", + "uri":"ddm_08_0003.html", "doc_type":"usermanual", "p_code":"89", "code":"91" @@ -966,7 +966,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"DML", - "uri":"ddm-08-0004.html", + "uri":"ddm_08_0004.html", "doc_type":"usermanual", "p_code":"89", "code":"108" @@ -975,7 +975,7 @@ "desc":"INSERT is used to insert data into database objects.INSERT DELAYED is not supported.Only INSERT statements that contain sharding fields are supported.PARTITION syntax is ", "product_code":"ddm", "title":"INSERT", - "uri":"ddm-08-0005.html", + "uri":"ddm_08_0005.html", "doc_type":"usermanual", "p_code":"108", "code":"109" @@ -984,7 +984,7 @@ "desc":"REPLACE is used to insert rows into or replace rows in a table.PARTITION syntax is not supported.If an auto-increment table has no ID, you can insert a data record with a", "product_code":"ddm", "title":"REPLACE", - "uri":"ddm-08-0007.html", + "uri":"ddm_08_0007.html", "doc_type":"usermanual", "p_code":"108", "code":"110" @@ -993,7 +993,7 @@ "desc":"DELETE is used to delete rows that meet conditions from a table.The WHERE clause does not support subqueries, including correlated and non-correlated subqueries.Data in r", "product_code":"ddm", "title":"DELETE", - "uri":"ddm-08-0008.html", + "uri":"ddm_08_0008.html", "doc_type":"usermanual", "p_code":"108", "code":"111" @@ -1002,7 +1002,7 @@ "desc":"Subqueries are not supported, including correlated and non-correlated subqueries.Cross-shard subquery is not supported.The WHERE condition in the UPDATE statement does no", "product_code":"ddm", "title":"UPDATE", - "uri":"ddm-08-0009.html", + "uri":"ddm_08_0009.html", "doc_type":"usermanual", "p_code":"108", "code":"112" @@ -1011,7 +1011,7 @@ "desc":"SELECT is generally used to query data in one or more tables.Supported syntaxSyntaxDescriptionselect_exprIndicates a column that you want to query.FROM table_referencesIn", "product_code":"ddm", "title":"SELECT", - "uri":"ddm-08-0006.html", + "uri":"ddm_08_0006.html", "doc_type":"usermanual", "p_code":"108", "code":"113" @@ -1020,7 +1020,7 @@ "desc":"table_references:table_reference:table_factor:join_table:join_condition:SELECT STRAIGHT_JOIN and NATURAL JOIN are not supported.", "product_code":"ddm", "title":"SELECT JOIN Syntax", - "uri":"ddm-08-0010.html", + "uri":"ddm_08_0010.html", "doc_type":"usermanual", "p_code":"108", "code":"114" @@ -1029,7 +1029,7 @@ "desc":"SELECT statements in UNION do not support duplicate column names.", "product_code":"ddm", "title":"SELECT UNION Syntax", - "uri":"ddm-08-0011.html", + "uri":"ddm_08_0011.html", "doc_type":"usermanual", "p_code":"108", "code":"115" @@ -1038,7 +1038,7 @@ "desc":"ExampleSyntaxExampleSyntaxExampleSyntaxExampleEach derived table must have an alias.A derived table cannot be a correlated subquery.In some cases, correct results cannot ", "product_code":"ddm", "title":"SELECT Subquery Syntax", - "uri":"ddm-08-0012.html", + "uri":"ddm_08_0012.html", "doc_type":"usermanual", "p_code":"108", "code":"116" @@ -1065,7 +1065,7 @@ "desc":"DDM is compatible with the MySQL license and syntax, but the use of SQL statements is limited due to differences between distributed databases and single-node databases.T", "product_code":"ddm", "title":"Use Constraints", - "uri":"ddm-08-0013.html", + "uri":"ddm_08_0013.html", "doc_type":"usermanual", "p_code":"89", "code":"119" @@ -1074,7 +1074,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"Supported SQL Statements", - "uri":"ddm-08-0002.html", + "uri":"ddm_08_0002.html", "doc_type":"usermanual", "p_code":"89", "code":"120" @@ -1083,7 +1083,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"CHECK TABLE", - "uri":"ddm-08-0014.html", + "uri":"ddm_08_0014.html", "doc_type":"usermanual", "p_code":"120", "code":"121" @@ -1092,7 +1092,7 @@ "desc":"Purpose: To check DDL consistency of all logical tables in one schemaCommand Format:Command Output:The following output is returned if DDL check results of all logical ta", "product_code":"ddm", "title":"Checking DDL Consistency of Physical Tables in All Logical Tables", - "uri":"ddm-08-0021.html", + "uri":"ddm_08_0021.html", "doc_type":"usermanual", "p_code":"121", "code":"122" @@ -1101,7 +1101,7 @@ "desc":"Purpose: To check DDL consistency of physical tables in a specific logical tableCommand Format:Command Output:If the returned result set is empty, DDL results of physical", "product_code":"ddm", "title":"Checking DDL Consistency of Physical Tables in One Logical Table", - "uri":"ddm-08-0022.html", + "uri":"ddm_08_0022.html", "doc_type":"usermanual", "p_code":"121", "code":"123" @@ -1110,7 +1110,7 @@ "desc":"Command Format 1:show rule;It is used to view the sharding rule of each logical table in a certain schema.Command output:Command Format 2:show rule from;It is", "product_code":"ddm", "title":"SHOW RULE", - "uri":"ddm-08-0015.html", + "uri":"ddm_08_0015.html", "doc_type":"usermanual", "p_code":"120", "code":"124" @@ -1119,7 +1119,7 @@ "desc":"Command Format:show topology from;It is used to view physical tables corresponding to a specified logical table.Output Details:RDS_instance_id: indicates the ", "product_code":"ddm", "title":"SHOW TOPOLOGY", - "uri":"ddm-08-0017.html", + "uri":"ddm_08_0017.html", "doc_type":"usermanual", "p_code":"120", "code":"125" @@ -1128,7 +1128,7 @@ "desc":"Command Format:show data node;It is used to view data about database shards in the RDS instance.Output Details:RDS_instance_id: indicates the ID of the RDS instance.PHYSI", "product_code":"ddm", "title":"SHOW DATA NODE", - "uri":"ddm-08-0029.html", + "uri":"ddm_08_0130.html", "doc_type":"usermanual", "p_code":"120", "code":"126" @@ -1137,7 +1137,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"TRUNCATE TABLE", - "uri":"ddm-08-0023.html", + "uri":"ddm_08_0023.html", "doc_type":"usermanual", "p_code":"120", "code":"127" @@ -1146,7 +1146,7 @@ "desc":"Command Format:/*+db=*/ TRUNCATE TABLEDescription:Deleting data in physical tables corresponding to in does ", "product_code":"ddm", "title":"HINT-DB", - "uri":"ddm-08-0024.html", + "uri":"ddm_08_0024.html", "doc_type":"usermanual", "p_code":"127", "code":"128" @@ -1155,7 +1155,7 @@ "desc":"HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way. This section describes how to use HINT syntax to delete ", "product_code":"ddm", "title":"HINT-TABLE", - "uri":"ddm-08-0025.html", + "uri":"ddm_08_0025.html", "doc_type":"usermanual", "p_code":"127", "code":"129" @@ -1164,7 +1164,7 @@ "desc":"Command Format:/*+db=,table=*/ TRUNCATE TABLEDescription:Deleting data in physical table in datab", "product_code":"ddm", "title":"HINT-DB/TABLE", - "uri":"ddm-08-0026.html", + "uri":"ddm_08_0026.html", "doc_type":"usermanual", "p_code":"127", "code":"130" @@ -1173,7 +1173,7 @@ "desc":"Command Format:/*+ allow_alter_rerun=true*/Description:Using this hint ensures that commands can be repeatedly executed, and no error is reported. This hint ", "product_code":"ddm", "title":"HINT- ALLOW_ALTER_RERUN", - "uri":"ddm-08-0027.html", + "uri":"ddm_08_0027.html", "doc_type":"usermanual", "p_code":"120", "code":"131" @@ -1350,7 +1350,7 @@ "code":"150" }, { - "desc":"Currently, you cannot connect to DDM using JDBC driver 5.1.46. Versions 5.1.35 to 5.1.45 are recommended.JDBC driver download address: https://dev.mysql.com/doc/index-con", + "desc":"Currently, you cannot connect to DDM using JDBC driver 5.1.46. Versions 5.1.35 to 5.1.45 are recommended.JDBC driver download address:https://dev.mysql.com/downloads/conn", "product_code":"ddm", "title":"What Version and Parameters Should I Select?", "uri":"ddm_04_0009.html", @@ -1524,7 +1524,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ddm", "title":"Change History", - "uri":"ddm_histroy_0003.html", + "uri":"ddm_history_0003.html", "doc_type":"usermanual", "p_code":"", "code":"170" diff --git a/docs/ddm/umn/ddm-08-0004.html b/docs/ddm/umn/ddm-08-0004.html deleted file mode 100644 index 5f67dfa3..00000000 --- a/docs/ddm/umn/ddm-08-0004.html +++ /dev/null @@ -1,31 +0,0 @@ - - -

DML

-
- - diff --git a/docs/ddm/umn/ddm-08-0008.html b/docs/ddm/umn/ddm-08-0008.html deleted file mode 100644 index f978704b..00000000 --- a/docs/ddm/umn/ddm-08-0008.html +++ /dev/null @@ -1,16 +0,0 @@ - - -

DELETE

-

DELETE is used to delete rows that meet conditions from a table.

-

Common Syntax

DELETE [IGNORE]
-FROM tbl_name [WHERE where_condition]
-
-

Syntax Restrictions

  • The WHERE clause does not support subqueries, including correlated and non-correlated subqueries.
  • Data in reference tables cannot be deleted when multiple tables are deleted at a time.
  • PARTITION clauses are not supported.
-
-
-
-
-
Parent topic: DML
-
-
- diff --git a/docs/ddm/umn/ddm-08-0009.html b/docs/ddm/umn/ddm-08-0009.html deleted file mode 100644 index c7d8fb8f..00000000 --- a/docs/ddm/umn/ddm-08-0009.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

UPDATE

-

Common Syntax

UPDATE table_reference
-SET col_name1={expr1} [, col_name2={expr2}] ...
-[WHERE where_condition]
-
-

Syntax Restrictions

  • Subqueries are not supported, including correlated and non-correlated subqueries.
  • Cross-shard subquery is not supported.
  • The WHERE condition in the UPDATE statement does not support arithmetic expressions and their subqueries.
  • Modifying broadcast tables is not supported during an update of multiple tables. (Data in columns of a broadcast table cannot be on the left of SET assignment statements).
  • Updating the sharding key field of a logical table is not supported because this operation may cause data redistribution.
  • Setting datetime to 1582 or any value smaller in UPDATE statements is not supported.
  • UPDATE cannot be used to update sharding key value DEFAULT.
  • Repeatedly updating the same field in an UPDATE statement is not supported.
  • Updating a sharding key using UPDATE JOIN syntax is not supported.
  • UPDATE cannot be used to update self-joins.
  • Referencing other object columns in assignment statements or expressions may cause unexpected update results. Example:

    update tbl_1 a,tbl_2 b set a.name=concat(b.name,'aaaa'),b.name=concat(a.name,'bbbb') on a.id=b.id

    -
  • UPDATE JOIN supports only joins with WHERE conditions.
-
-
-
-
-
Parent topic: DML
-
-
- diff --git a/docs/ddm/umn/ddm-08-0013.html b/docs/ddm/umn/ddm-08-0013.html deleted file mode 100644 index ccd9ead0..00000000 --- a/docs/ddm/umn/ddm-08-0013.html +++ /dev/null @@ -1,16 +0,0 @@ - - -

Use Constraints

-

DDM is compatible with the MySQL license and syntax, but the use of SQL statements is limited due to differences between distributed databases and single-node databases.

-

Unsupported SQL Statements

  • Triggers
  • Temporary tables
  • DO statement
  • Association with foreign keys
  • RESET statement
  • FLUSH statement
  • BINLOG statement
  • HANDLER statement
  • SHOW WARNINGS statement
  • Assignment operator :=
  • Operators less than (<), assignment (=), and more than (>)
  • Expression IS UNKNOWN
  • INSTALL and UNINSTALL PLUGIN statements
  • Cross-shard stored procedures and custom functions
  • Statements for modifying database names, table names, and sharding field names and types
  • Most of SHOW statements such as SHOW PROFILES and SHOW ERRORS
  • Table maintenance statements, including ANALYZE, CHECK, CHECKSUM, OPTIMIZE, and REPAIR TABLE
  • Statements for assigning a value to or querying variable session, for example, set @rowid=0;select @rowid:=@rowid+1,id from user
  • SQL statements that use -- or /*...*/ to comment out a single line or multiple lines of code
  • The result of the REPEAT function contains a maximum of 1,000,000 characters (in version 3.0.9 or later).
-
-

Permission Levels

Permission levels supported by DDM are as follows:

-
  • Global level (not supported)
  • Database level (supported)
  • Table level (supported)
  • Column level (not supported)
  • Subprogram level (not supported)
  • User level (supported)
-
-
-
-
-
Parent topic: SQL Syntax
-
-
- diff --git a/docs/ddm/umn/ddm-08-0015.html b/docs/ddm/umn/ddm-08-0015.html deleted file mode 100644 index 3e563e29..00000000 --- a/docs/ddm/umn/ddm-08-0015.html +++ /dev/null @@ -1,32 +0,0 @@ - - -

SHOW RULE

-

Command Format 1:

-

show rule;

-

It is used to view the sharding rule of each logical table in a certain schema.

-

Command output:

-

-

Command Format 2:

-

show rule from <table_name>;

-

It is used to view the sharding rule of a specific logical table in a certain schema.

-

Command output:

-

-

Output Details:

-

TABLE_NAME: indicates the name of the logical table.

-

BROADCAST: specifies whether the table is a broadcast table. 0 indicates that the table is not a broadcast table. 1 indicates the table is a broadcast table.

-

DB_PARTITION_KEY: indicates the database sharding key. Leave this field blank if database sharding is not required.

-

DB_PARTITION_POLICY: indicates the database sharding algorithm. The value can be HASH, YYYYMM, YYYYDD, and YYYYWEEK.

-

DB_PARTITION_COUNT: indicates the number of database shards.

-

DB_PARTITION_OFFSET: indicates where a new database shard starts from.

-

PARTITION_RANGE: indicates the sharding range when the database sharding algorithm is range.

-

TB_PARTITION_KEY: indicates the table sharding key. Leave this field blank if table sharding is not required.

-

TB_PARTITION_POLICY: indicates the table sharding algorithm. The value can be HASH, MM, DD, MMDD, or WEEK.

-

TB_PARTITION_COUNT: indicates the number of physical tables in each database shard.

-

TB_PARTITION_OFFSET: indicates where a new physical table starts from.

-
-
-
-
Parent topic: Supported SQL Statements
-
-
- diff --git a/docs/ddm/umn/ddm-08-0017.html b/docs/ddm/umn/ddm-08-0017.html deleted file mode 100644 index 67b58d8d..00000000 --- a/docs/ddm/umn/ddm-08-0017.html +++ /dev/null @@ -1,20 +0,0 @@ - - -

SHOW TOPOLOGY

-

Command Format:

-

show topology from <table_name>;

-

It is used to view physical tables corresponding to a specified logical table.

-

Output Details:

-

RDS_instance_id: indicates the ID of the RDS instance.

-

HOST: indicates the IP address of the RDS instance.

-

PORT: indicates the port number of the RDS instance.

-

DATABASE: indicates the physical database in the RDS instance.

-

TABLE: indicates the physical table.

-

ROW_COUNT: indicates the estimated number of data entries in each physical table. The value is obtained from information_schema.TABLES.

-
-
-
-
Parent topic: Supported SQL Statements
-
-
- diff --git a/docs/ddm/umn/ddm-08-0021.html b/docs/ddm/umn/ddm-08-0021.html deleted file mode 100644 index 76ba520f..00000000 --- a/docs/ddm/umn/ddm-08-0021.html +++ /dev/null @@ -1,22 +0,0 @@ - - -

Checking DDL Consistency of Physical Tables in All Logical Tables

-

Purpose: To check DDL consistency of all logical tables in one schema

-

Command Format:

-
 check table
-

Command Output:

-

The following output is returned if DDL check results of all logical tables are consistent.

-

-

The following output is returned if there are logical tables with inconsistent DDL check results.

-

-

Output Details:

-

Each row contains the check result of a logical table.

-
  • DATABASE_NAME: indicates the schema name.
  • TABLE_NAME: indicates the logical table name.
  • TABLE_TYPE: indicates the logical table type.
    • SINGLE: indicates that the logical table is unsharded.
    • BROADCAST: indicates that the table is a broadcast table.
    • SHARDING: indicates that the table is sharded.
    -
  • DDL_CONSISTENCY: indicates whether DDL results of all physical tables corresponding to the logical table are consistent.
  • TOTAL_COUNT: indicates the number of physical tables in the logical table.
  • INCONSISTENT_COUNT: indicates the number of physical tables with inconsistent DDL results.
  • DETAILS: indicates names of the physical tables with inconsistent DDL check results.
-
-
-
-
Parent topic: CHECK TABLE
-
-
- diff --git a/docs/ddm/umn/ddm-08-0022.html b/docs/ddm/umn/ddm-08-0022.html deleted file mode 100644 index 6f1f7523..00000000 --- a/docs/ddm/umn/ddm-08-0022.html +++ /dev/null @@ -1,21 +0,0 @@ - - -

Checking DDL Consistency of Physical Tables in One Logical Table

-

Purpose: To check DDL consistency of physical tables in a specific logical table

-

Command Format:

-
check table <table_name>
-

Command Output:

-

If the returned result set is empty, DDL results of physical tables in this logical table are consistent.

-

-

If the returned result set is not empty, there are physical tables with inconsistent DDL results.

-

-

Output Details:

-

Each row displays details of a physical table with inconsistent DDL results.

-
  • DATABASE_NAME: indicates the database shard containing the physical table.
  • TABLE_NAME: indicates the name of the physical table.
  • TABLE_TYPE: indicates the type of the logical table that the physical table belongs to.
  • EXTRA_COLUMNS: indicates extra columns in the physical table.
  • MISSING_COLUMNS: indicates missing columns in the physical table.
  • DIFFERENT_COLUMNS: indicates name and type columns whose attributes are inconsistent in the physical table.
  • KEY_DIFF: indicates inconsistent indexes in the physical table.
  • ENGINE_DIFF: indicates inconsistent engines in the physical table.
  • CHARSET_DIFF: indicates inconsistent character sets in the physical table.
  • COLLATE_DIFF: indicates inconsistent collations in the physical table.
  • EXTRA_PARTITIONS: indicates extra partitions in the physical table. This field is only available to partitioned tables.
  • MISSING_PARTITIONS: indicates missing partitions in the physical table. This field is only available to partitioned tables.
  • DIFFERENT_PARTITIONS: indicates partitions with inconsistent attributes in the physical table. This field is only available to partitioned tables.
  • EXTRA_INFO: indicates other information such as missing physical tables.
-
-
-
-
Parent topic: CHECK TABLE
-
-
- diff --git a/docs/ddm/umn/ddm-08-0024.html b/docs/ddm/umn/ddm-08-0024.html deleted file mode 100644 index c103ece0..00000000 --- a/docs/ddm/umn/ddm-08-0024.html +++ /dev/null @@ -1,16 +0,0 @@ - - -

HINT-DB

-

Command Format:

-

/*+db=<physical_db_name>*/ TRUNCATE TABLE <table_name>

-

Description:

-

Deleting data in physical tables corresponding to <table_name> in <physical_db_name> does not affect physical tables in other database shards.

-

HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way.

-
-
-
-
-
Parent topic: TRUNCATE TABLE
-
-
- diff --git a/docs/ddm/umn/ddm-08-0025.html b/docs/ddm/umn/ddm-08-0025.html deleted file mode 100644 index 209456eb..00000000 --- a/docs/ddm/umn/ddm-08-0025.html +++ /dev/null @@ -1,21 +0,0 @@ - - -

HINT-TABLE

-

HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way. This section describes how to use HINT syntax to delete data from a table.

-

Command Format:

-

/*+table=<physical_table_name>*/ TRUNCATE TABLE <table_name>

-

Description:

-

Deleting data in physical table <physical_table_name> in the current database shard does not affect other physical tables.

-

Example output before the table is deleted:

-

-

Example output after the table is deleted:

-

-

Hints are valid only for sharded tables.

-
-
-
-
-
Parent topic: TRUNCATE TABLE
-
-
- diff --git a/docs/ddm/umn/ddm-08-0026.html b/docs/ddm/umn/ddm-08-0026.html deleted file mode 100644 index 264e57eb..00000000 --- a/docs/ddm/umn/ddm-08-0026.html +++ /dev/null @@ -1,16 +0,0 @@ - - -

HINT-DB/TABLE

-

Command Format:

-

/*+db=<physical_db_name>,table=<physical_table_name>*/ TRUNCATE TABLE <table_name>

-

Description:

-

Deleting data in physical table <physical_table_name> in database shard <physical_db_name> does not affect other physical tables.

-

Hints are valid only for sharded tables.

-
-
-
-
-
Parent topic: TRUNCATE TABLE
-
-
- diff --git a/docs/ddm/umn/ddm-08-0029.html b/docs/ddm/umn/ddm-08-0029.html deleted file mode 100644 index b61f180f..00000000 --- a/docs/ddm/umn/ddm-08-0029.html +++ /dev/null @@ -1,18 +0,0 @@ - - -

SHOW DATA NODE

-

Command Format:

-

show data node;

-

It is used to view data about database shards in the RDS instance.

-

Output Details:

-

RDS_instance_id: indicates the ID of the RDS instance.

-

PHYSICAL_NODE: used to view physical databases in the RDS instance.

-

HOST: indicates the IP address of the RDS instance.

-

PORT: indicates the port number of the RDS instance.

-
-
-
-
Parent topic: Supported SQL Statements
-
-
- diff --git a/docs/ddm/umn/ddm_01_0000.html b/docs/ddm/umn/ddm_01_0000.html index fa31387c..a6f06ba4 100644 --- a/docs/ddm/umn/ddm_01_0000.html +++ b/docs/ddm/umn/ddm_01_0000.html @@ -12,11 +12,11 @@
  • Product Specifications
    • -
  • Usage Constraints
    +
  • Usage Constraints
  • Regions and AZs
    • -
  • Application Scenarios
    +
  • Application Scenarios
    • diff --git a/docs/ddm/umn/ddm-01-0002.html b/docs/ddm/umn/ddm_01_0002.html similarity index 72% rename from docs/ddm/umn/ddm-01-0002.html rename to docs/ddm/umn/ddm_01_0002.html index 588badc1..d9227360 100644 --- a/docs/ddm/umn/ddm-01-0002.html +++ b/docs/ddm/umn/ddm_01_0002.html @@ -1,10 +1,10 @@ - +

    Application Scenarios

    -

    It is especially suitable for applications requiring high-concurrency access to large volumes of data. Typical application scenarios are as follows:

    -
    • Internet

      E-commerce, finance, O2O, retail, and social networking applications usually face challenges such as large user base, frequent marketing events, and slow response of core transactional systems. DDM can scale compute and storage resources to improve database processing of high-concurrency transactions and ensure fast access to data.

      -
    • IoT

      In industrial monitoring, remote control, smart city extension, smart home, and Internet of Vehicles (IoV) scenarios, a large number of sensors and monitoring devices frequently collect data and generate huge amounts of data, which may exceed the storage capability of single-node databases. DDM provides horizontal expansion to help you store massive data at low costs.

      -
    • Traditional sectors

      Government agencies, large-sized enterprises, banks, and the like usually use commercial solutions to support high-concurrency access to large volumes of data. These solutions are expensive because they need to rely on mid-range computers and high-end storage devices. DDM, deployed in clusters with common ECSs, provides cost-efficient database solutions with the same or even higher performance than traditional commercial database solutions.

      +

      It is especially suitable for applications requiring high-concurrency access to large volumes of data. Typical application scenarios are as follows:

      +
      • Internet

        E-commerce, finance, O2O, retail, and social networking applications usually face challenges such as large user base, frequent marketing events, and slow response of core transactional systems. DDM can scale compute and storage resources to improve database processing of high-concurrency transactions and ensure fast access to data.

        +
      • IoT

        In industrial monitoring, remote control, smart city extension, smart home, and Internet of Vehicles (IoV) scenarios, a large number of sensors and monitoring devices frequently collect data and generate huge amounts of data, which may exceed the storage capability of single-node databases. DDM provides horizontal expansion to help you store massive data at low costs.

        +
      • Traditional sectors

        Government agencies, large-sized enterprises, banks, and the like usually use commercial solutions to support high-concurrency access to large volumes of data. These solutions are expensive because they need to rely on mid-range computers and high-end storage devices. DDM, deployed in clusters with common ECSs, provides cost-efficient database solutions with the same or even higher performance than traditional commercial database solutions.

      diff --git a/docs/ddm/umn/ddm-01-0003.html b/docs/ddm/umn/ddm_01_0003.html similarity index 84% rename from docs/ddm/umn/ddm-01-0003.html rename to docs/ddm/umn/ddm_01_0003.html index 197225e2..b52528df 100644 --- a/docs/ddm/umn/ddm-01-0003.html +++ b/docs/ddm/umn/ddm_01_0003.html @@ -1,10 +1,10 @@ - +

      Usage Constraints

        -
      • Network Access
        +
      • Network Access
      • Data Nodes
        • diff --git a/docs/ddm/umn/ddm-01-0004.html b/docs/ddm/umn/ddm_01_0004.html similarity index 59% rename from docs/ddm/umn/ddm-01-0004.html rename to docs/ddm/umn/ddm_01_0004.html index 6f0896c8..b6ce098c 100644 --- a/docs/ddm/umn/ddm-01-0004.html +++ b/docs/ddm/umn/ddm_01_0004.html @@ -1,12 +1,12 @@ - +

        Network Access

        -

        Restrictions on network access are as follows:

        -
        • The data nodes and ECSs running your applications must be in the same VPC as your DDM instance.
        • To access DDM from your computer, you need to bind an EIP to your DDM instance and then use the EIP to access the DDM instance.
        +

        Restrictions on network access are as follows:

        +
        • The data nodes and ECSs running your applications must be in the same VPC as your DDM instance.
        • To access DDM from your computer, you need to bind an EIP to your DDM instance and then use the EIP to access the DDM instance.
        -
        Parent topic: Usage Constraints
        +
        Parent topic: Usage Constraints
        diff --git a/docs/ddm/umn/ddm_01_0005.html b/docs/ddm/umn/ddm_01_0005.html index 07e6ca30..be5a18b8 100644 --- a/docs/ddm/umn/ddm_01_0005.html +++ b/docs/ddm/umn/ddm_01_0005.html @@ -8,7 +8,7 @@
        -
        Parent topic: Usage Constraints
        +
        Parent topic: Usage Constraints
        diff --git a/docs/ddm/umn/ddm_01_0174.html b/docs/ddm/umn/ddm_01_0174.html index 5bbe6db2..eee8f0c8 100644 --- a/docs/ddm/umn/ddm_01_0174.html +++ b/docs/ddm/umn/ddm_01_0174.html @@ -69,7 +69,7 @@ ON DUPLICATE KEY UPDATE b = b + c;
      -
      Parent topic: Usage Constraints
      +
      Parent topic: Usage Constraints
      diff --git a/docs/ddm/umn/ddm_01_0175.html b/docs/ddm/umn/ddm_01_0175.html index 1d44b7df..6601239b 100644 --- a/docs/ddm/umn/ddm_01_0175.html +++ b/docs/ddm/umn/ddm_01_0175.html @@ -6,7 +6,7 @@
      -
      Parent topic: Usage Constraints
      +
      Parent topic: Usage Constraints
      diff --git a/docs/ddm/umn/ddm_03_0030.html b/docs/ddm/umn/ddm_03_0030.html index 116b0d6c..9924cf9a 100644 --- a/docs/ddm/umn/ddm_03_0030.html +++ b/docs/ddm/umn/ddm_03_0030.html @@ -13,7 +13,7 @@
    -
    Parent topic: SQL Syntax
    +
    Parent topic: SQL Syntax
    diff --git a/docs/ddm/umn/ddm_03_0031.html b/docs/ddm/umn/ddm_03_0031.html index 5cb8bdcf..55ec2bf4 100644 --- a/docs/ddm/umn/ddm_03_0031.html +++ b/docs/ddm/umn/ddm_03_0031.html @@ -24,7 +24,7 @@
    -
    Parent topic: Supported SQL Statements
    +
    Parent topic: Supported SQL Statements
    diff --git a/docs/ddm/umn/ddm_03_0032.html b/docs/ddm/umn/ddm_03_0032.html index 31c42a43..925ff1d0 100644 --- a/docs/ddm/umn/ddm_03_0032.html +++ b/docs/ddm/umn/ddm_03_0032.html @@ -28,7 +28,7 @@
    -
    Parent topic: SQL Syntax
    +
    Parent topic: SQL Syntax
    diff --git a/docs/ddm/umn/ddm_03_0034.html b/docs/ddm/umn/ddm_03_0034.html index ccf84c5c..2002bbdb 100644 --- a/docs/ddm/umn/ddm_03_0034.html +++ b/docs/ddm/umn/ddm_03_0034.html @@ -14,7 +14,7 @@
    -
    Parent topic: Supported SQL Statements
    +
    Parent topic: Supported SQL Statements
    diff --git a/docs/ddm/umn/ddm_03_0035.html b/docs/ddm/umn/ddm_03_0035.html index d24ddcf9..eb9fa548 100644 --- a/docs/ddm/umn/ddm_03_0035.html +++ b/docs/ddm/umn/ddm_03_0035.html @@ -21,7 +21,7 @@
    -
    Parent topic: SQL Syntax
    +
    Parent topic: SQL Syntax
    diff --git a/docs/ddm/umn/ddm_03_0038.html b/docs/ddm/umn/ddm_03_0038.html index 21564502..d11eeffc 100644 --- a/docs/ddm/umn/ddm_03_0038.html +++ b/docs/ddm/umn/ddm_03_0038.html @@ -503,7 +503,7 @@
    -
    Parent topic: DDL
    +
    Parent topic: DDL
    diff --git a/docs/ddm/umn/ddm_03_0039.html b/docs/ddm/umn/ddm_03_0039.html index aa22e6b9..3eca55b7 100644 --- a/docs/ddm/umn/ddm_03_0039.html +++ b/docs/ddm/umn/ddm_03_0039.html @@ -8,7 +8,7 @@
    -
    Parent topic: Supported SQL Statements
    +
    Parent topic: Supported SQL Statements
    diff --git a/docs/ddm/umn/ddm_03_0040.html b/docs/ddm/umn/ddm_03_0040.html index a462c4ac..28b5518e 100644 --- a/docs/ddm/umn/ddm_03_0040.html +++ b/docs/ddm/umn/ddm_03_0040.html @@ -12,7 +12,7 @@
    -
    Parent topic: Supported SQL Statements
    +
    Parent topic: Supported SQL Statements
    diff --git a/docs/ddm/umn/ddm_03_0053.html b/docs/ddm/umn/ddm_03_0053.html index 0cf7c662..dff7b163 100644 --- a/docs/ddm/umn/ddm_03_0053.html +++ b/docs/ddm/umn/ddm_03_0053.html @@ -37,7 +37,7 @@

    Flexible shards configuration for a schema

    -

    You can increase shards or data nodes to scale out storage. For details, see Shard Configuration.

    +

    You can increase shards or data nodes to scale out storage. For details, see Shard Configuration.

    Accounts

    @@ -52,7 +52,7 @@

    SQL syntax

    -

    Describing DDL, DML, global sequence, SQL statements, and sharding algorithms. For details, see SQL Syntax.

    +

    Describing DDL, DML, global sequence, SQL statements, and sharding algorithms. For details, see SQL Syntax.

    diff --git a/docs/ddm/umn/ddm_03_0062.html b/docs/ddm/umn/ddm_03_0062.html index 46dba35f..1ea48759 100644 --- a/docs/ddm/umn/ddm_03_0062.html +++ b/docs/ddm/umn/ddm_03_0062.html @@ -73,7 +73,7 @@
    -
    Parent topic: SQL Syntax
    +
    Parent topic: SQL Syntax
    diff --git a/docs/ddm/umn/ddm_03_0063.html b/docs/ddm/umn/ddm_03_0063.html index e6d938c7..ec21c09a 100644 --- a/docs/ddm/umn/ddm_03_0063.html +++ b/docs/ddm/umn/ddm_03_0063.html @@ -202,7 +202,7 @@
    -
    Parent topic: SQL Syntax
    +
    Parent topic: SQL Syntax
    diff --git a/docs/ddm/umn/ddm_03_0067.html b/docs/ddm/umn/ddm_03_0067.html index e414d54d..5fb392aa 100644 --- a/docs/ddm/umn/ddm_03_0067.html +++ b/docs/ddm/umn/ddm_03_0067.html @@ -4,9 +4,9 @@
    diff --git a/docs/ddm/umn/ddm_03_0068.html b/docs/ddm/umn/ddm_03_0068.html index 7ad1bbf9..aa36f308 100644 --- a/docs/ddm/umn/ddm_03_0068.html +++ b/docs/ddm/umn/ddm_03_0068.html @@ -20,7 +20,7 @@
    -
    Parent topic: Shard Configuration
    +
    Parent topic: Shard Configuration
    diff --git a/docs/ddm/umn/ddm_03_0069.html b/docs/ddm/umn/ddm_03_0069.html index bdabdd90..cb02946b 100644 --- a/docs/ddm/umn/ddm_03_0069.html +++ b/docs/ddm/umn/ddm_03_0069.html @@ -6,7 +6,7 @@
    -
    Parent topic: Shard Configuration
    +
    Parent topic: Shard Configuration
    diff --git a/docs/ddm/umn/ddm_03_0070.html b/docs/ddm/umn/ddm_03_0070.html index 7baf87c8..178a8261 100644 --- a/docs/ddm/umn/ddm_03_0070.html +++ b/docs/ddm/umn/ddm_03_0070.html @@ -104,7 +104,7 @@
    -
    Parent topic: Shard Configuration
    +
    Parent topic: Shard Configuration
    diff --git a/docs/ddm/umn/ddm_03_0071.html b/docs/ddm/umn/ddm_03_0071.html index e56dfc80..16d8c40a 100644 --- a/docs/ddm/umn/ddm_03_0071.html +++ b/docs/ddm/umn/ddm_03_0071.html @@ -33,7 +33,7 @@
    -
    Parent topic: Shard Configuration
    +
    Parent topic: Shard Configuration
    diff --git a/docs/ddm/umn/ddm_03_0064.html b/docs/ddm/umn/ddm_03_0131.html similarity index 90% rename from docs/ddm/umn/ddm_03_0064.html rename to docs/ddm/umn/ddm_03_0131.html index 70c71305..5e844439 100644 --- a/docs/ddm/umn/ddm_03_0064.html +++ b/docs/ddm/umn/ddm_03_0131.html @@ -1,4 +1,4 @@ - +

    Shard Configuration

    diff --git a/docs/ddm/umn/ddm_04_0009.html b/docs/ddm/umn/ddm_04_0009.html index b8f6384c..0087cdc2 100644 --- a/docs/ddm/umn/ddm_04_0009.html +++ b/docs/ddm/umn/ddm_04_0009.html @@ -2,7 +2,7 @@

    What Version and Parameters Should I Select?

    Currently, you cannot connect to DDM using JDBC driver 5.1.46. Versions 5.1.35 to 5.1.45 are recommended.

    -

    JDBC driver download address: https://dev.mysql.com/doc/index-connectors.html

    +

    JDBC driver download address:https://dev.mysql.com/downloads/connector/j/

    Table 1 describes the recommended parameters for the JDBC URL.

    Table 1 Parameters

    Parameter

    diff --git a/docs/ddm/umn/ddm_05_0001.html b/docs/ddm/umn/ddm_05_0001.html index 5ad59b10..b0f74a1b 100644 --- a/docs/ddm/umn/ddm_05_0001.html +++ b/docs/ddm/umn/ddm_05_0001.html @@ -6,9 +6,9 @@
    • Creating an Account
      • -
    • Modifying an Account
      +
    • Modifying an Account
      • -
    • Deleting an Account
      +
    • Deleting an Account
    • Resetting the Password of an Account
      • diff --git a/docs/ddm/umn/ddm_05_0003.html b/docs/ddm/umn/ddm_05_0003.html deleted file mode 100644 index 72b1216b..00000000 --- a/docs/ddm/umn/ddm_05_0003.html +++ /dev/null @@ -1,15 +0,0 @@ - - -

      Modifying an Account

      -

      Prerequisites

      You have logged in to the DDM console.

      -
      -

      Procedure

      1. In the instance list, locate the DDM instance that you want to modify and click its name.
      2. In the navigation pane, choose Accounts.
      3. In the account list, locate the required account and click Modify in the Operation column.
      4. In the displayed dialog box, modify the associated schemas, permissions, and description.

        -

      5. Click OK.
      -
      -
      -
      -
      -
      Parent topic: Account Management
      -
      -
      - diff --git a/docs/ddm/umn/ddm_05_0004.html b/docs/ddm/umn/ddm_05_0004.html deleted file mode 100644 index 7b0eca94..00000000 --- a/docs/ddm/umn/ddm_05_0004.html +++ /dev/null @@ -1,16 +0,0 @@ - - -

      Deleting an Account

      -

      Prerequisites

      You have logged in to the DDM console.

      -

      Deleted accounts cannot be recovered. Exercise caution when performing this operation.

      -
      -
      -

      Procedure

      1. In the instance list, locate the DDM instance with the account that you want to delete and click its name.
      2. In the navigation pane, choose Accounts.
      3. In the account list, locate the account that you want to delete and choose More > Delete in the Operation column.
      4. In the displayed dialog box, click Yes.
      -
      -
      -
      -
      -
      Parent topic: Account Management
      -
      -
      - diff --git a/docs/ddm/umn/ddm_05_0133.html b/docs/ddm/umn/ddm_05_0133.html new file mode 100644 index 00000000..ac8a46a2 --- /dev/null +++ b/docs/ddm/umn/ddm_05_0133.html @@ -0,0 +1,15 @@ + + +

      Modifying an Account

      +

      Prerequisites

      You have logged in to the DDM console.

      +
      +

      Procedure

      1. In the instance list, locate the DDM instance that you want to modify and click its name.
      2. In the navigation pane, choose Accounts.
      3. In the account list, locate the required account and click Modify in the Operation column.
      4. In the displayed dialog box, modify the associated schemas, permissions, and description.

        +

      5. Click OK.
      +
      +
      +
      +
      +
      Parent topic: Account Management
      +
      +
      + diff --git a/docs/ddm/umn/ddm_05_0134.html b/docs/ddm/umn/ddm_05_0134.html new file mode 100644 index 00000000..ae8c1960 --- /dev/null +++ b/docs/ddm/umn/ddm_05_0134.html @@ -0,0 +1,16 @@ + + +

      Deleting an Account

      +

      Prerequisites

      You have logged in to the DDM console.

      +

      Deleted accounts cannot be recovered. Exercise caution when performing this operation.

      +
      +
      +

      Procedure

      1. In the instance list, locate the DDM instance with the account that you want to delete and click its name.
      2. In the navigation pane, choose Accounts.
      3. In the account list, locate the account that you want to delete and choose More > Delete in the Operation column.
      4. In the displayed dialog box, click Yes.
      +
      +
      +
      +
      +
      Parent topic: Account Management
      +
      +
      + diff --git a/docs/ddm/umn/ddm_0600017.html b/docs/ddm/umn/ddm_0600017.html deleted file mode 100644 index d257fd23..00000000 --- a/docs/ddm/umn/ddm_0600017.html +++ /dev/null @@ -1,72 +0,0 @@ - - -

      Restoring Metadata

      -

      DDM automatically backs up DDM instance metadata at 02:00 UTC+00:00 every day and retains the backup data for 30 days. Metadata backup is also triggered by key operations that affect metadata, such as deleting a schema, deleting data after shard configuration, and deleting instances.

      -

      When you delete a schema by mistake or your RDS for MySQL instances become abnormal, metadata restoration allows you to restore your DDM instance metadata and match the metadata with the RDS instance that has completed PITR to re-establish the relationship between your DDM instance and RDS instance. Metadata restoration supports only RDS for MySQL.

      -

      To restore metadata of a DDM instance, you can specify a point in time by referring to Restoring Metadata to a Point in Time, or using an available backup by referring to Restoring Metadata Using an Available Backup.

      -

      Precautions

      • Metadata restoration mainly restores the metadata of your DDM instance to a new DDM instance. It starts after a point-in-time recovery (PITR) for the associated data nodes is complete.

        PITR indicates that a data node has been restored to a specified point in time.

        -
        -
      • The destination DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.
      • Ensure that the selected RDS for MySQL instance has completed PITR.
      • Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.
      • The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.
      • Time points that data can be restored to depend on the backup policy set on original data nodes.
      -
      -

      Restoring Metadata to a Point in Time

      1. Log in to the DDM console.
      2. Create a new DDM instance.
      3. In the DDM instance list, locate the newly-created instance and click its name.
      4. In the navigation pane on the left, choose Backups & Restorations.
      5. Click Restore Metadata.
      6. On the displayed page, specify a time point. DDM will select an appropriate DDM metadata backup closest to the time point.

        -

        - - - - - - - - - - - - - -
        Table 1 Parameter description

        Parameter

        -

        Description

        -

        Restore To

        -

        Specify a point in time. DDM will restore metadata to this point in time using the most recent backup.

        -

        Destination DDM Instance

        -

        Select the DDM instance created in 2 as the destination instance.

        -

        Destination Data Nodes

        -

        Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.

        -
        -
        -

      7. Click OK. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.
      -
      -

      Restoring Metadata Using an Available Backup

      1. Log in to the DDM console.
      2. Create a new DDM instance.
      3. In the navigation pane on the left, choose Backups.
      4. Locate the required backup based on the instance name and backup time and click Restore in the Operation column.

        -

      5. On the displayed page, configure required parameters.

        -

        - - - - - - - - - - - - - -
        Table 2 Parameter description

        Parameter

        -

        Description

        -

        Backup Name

        -

        Name of the backup to be restored.

        -

        Destination DDM Instance

        -

        Select the DDM instance created in 2 as the destination instance.

        -

        Destination Data Nodes

        -

        Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.

        -
        -
        -

      6. Click OK. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.
      -
      -
      -
      -
      -
      Parent topic: Backups and Restorations
      -
      -
      - diff --git a/docs/ddm/umn/ddm_06_0001.html b/docs/ddm/umn/ddm_06_0001.html index f01d7200..0a1b835b 100644 --- a/docs/ddm/umn/ddm_06_0001.html +++ b/docs/ddm/umn/ddm_06_0001.html @@ -4,7 +4,7 @@
        -
      • Creating a DDM Instance
        +
      • Creating a DDM Instance
      • Splitting Read-only and Read-Write Services
        • diff --git a/docs/ddm/umn/ddm_06_00017.html b/docs/ddm/umn/ddm_06_00017.html deleted file mode 100644 index a17e9b36..00000000 --- a/docs/ddm/umn/ddm_06_00017.html +++ /dev/null @@ -1,94 +0,0 @@ - - -

        Creating a DDM Instance

        -

        Prerequisites

        You have logged in to the DDM console.

        -
        -

        Procedure

        1. On the displayed page, in the upper right corner, click Create DDM Instance.
        2. On the displayed page, configure the required parameters.

          -

          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
          Table 1 Parameter description

          Parameter

          -

          Description

          -

          Region

          -

          Region where the DDM instance is located. Select the required region.

          -

          AZ

          -

          Availability zone where the DDM instance is deployed.

          -

          Nodes in a DDM instance can be deployed on different physical servers in the same AZ to keep services always available even if one physical server becomes faulty.

          -

          A DDM instance can be deployed across AZs to provide cross-AZ DR.

          -

          If necessary, you can select multiple AZs when you create a DDM instance. Then nodes of the instance will be deployed in multiple different AZs.

          -
          NOTE:

          Deploy your application, DDM instance, and required RDS instances in the same AZ to reduce network latency. Cross-AZ deployment may increase network latency.

          -
          -

          Instance Name

          -

          Name of the DDM instance, which:

          -
          • Cannot be left blank.
          • Must start with a letter.
          • Must be 4 to 64 characters long.
          • Can contain only letters, digits, and hyphens (-).
          -

          Node Class

          -

          Class of the DDM instance node. You can select General-enhanced or Kunpeng general computing-plus and then specify a node class.

          -
          NOTE:

          Estimate compute and storage requirements of your applications based on your service type and scale before you create a DDM instance, and then select an appropriate node class so that the CPU and memory specifications of your DDM instance can better meet your needs.

          -
          -

          Instance Nodes

          -

          Number of nodes in a DDM instance. Up to 32 nodes are supported.

          -
          NOTE:

          At least 2 nodes are recommended because using a single node cannot guarantee high availability.

          -
          -

          VPC

          -

          VPC that the DDM instance belongs to. This VPC isolates networks for different services. It allows you to manage and configure private networks, simplifying network management.

          -

          Click View VPC to show more details and security group rules.

          -
          NOTE:

          The DDM instance should be in the same VPC as the required RDS for MySQL instance.

          -

          To ensure network connectivity, the DDM instance you purchased must be in the same VPC as your applications and RDS for MySQL instances.

          -
          -

          Subnet

          -

          Name and IP address range of the subnet

          -

          Security Group

          -

          Select an existing security group.

          -

          You are advised to select the same security group for your DDM instance, application, and RDS for MySQL instances so that they can communicate with each other. If different security groups are selected, add security group rules to enable network access.

          -

          Parameter Template

          -

          Select an existing parameter template. You can also click View Parameter Template to set parameters on the displayed page.

          -

          Tags

          -

          (Optional) Adding tags helps you better identify and manage your DDM resources.

          -

          You can add tags to your instance. Each instance can have a maximum of 20 tags.

          -

          Tag key: This parameter is mandatory and cannot be null.

          -
          • Must be unique for each instance.
          • Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
          • Can include 1 to 36 characters.
          • Cannot be an empty string or start with _sys_.
          -
          Tag value: This parameter is mandatory.
          • Is an empty string by default.
          • Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
          • Can contain 0 to 43 characters.
          -
          -
          -
          -

        3. After the configuration is complete, click Create Now at the bottom of the page.
        4. Confirm the configurations and click Submit.
        -
        -
        -
        -
        -
        Parent topic: Instance Management
        -
        -
        - diff --git a/docs/ddm/umn/ddm_0600016.html b/docs/ddm/umn/ddm_06_0016.html similarity index 55% rename from docs/ddm/umn/ddm_0600016.html rename to docs/ddm/umn/ddm_06_0016.html index f2891bec..a9160d22 100644 --- a/docs/ddm/umn/ddm_0600016.html +++ b/docs/ddm/umn/ddm_06_0016.html @@ -1,47 +1,47 @@ - +

        Restoring Data to a New Instance

        -

        DDM allows you to restore data from the current instance to any point in time using an existing backup. This is a good choice for routine service backup and restoration.

        -

        This section uses an RDS for MySQL instance as an example to describe how to restore data to a new DDM instance.

        -

        Precautions

        • Restoring data to a new instance restores your DDM instance and its data nodes (RDS for MySQL instances). Before the restoration, you need to prepare a new DDM instance and as many new RDS for MySQL instances as there are data nodes.
        +

        DDM allows you to restore data from the current instance to any point in time using an existing backup. This is a good choice for routine service backup and restoration.

        +

        This section uses an RDS for MySQL instance as an example to describe how to restore data to a new DDM instance.

        +

        Precautions

        • Restoring data to a new instance restores your DDM instance and its data nodes (RDS for MySQL instances). Before the restoration, you need to prepare a new DDM instance and as many new RDS for MySQL instances as there are data nodes.
        -
        • Restoring data to a new DDM instance will overwrite data on it and cause the instance to be unavailable during restoration.
        • The new RDS for MySQL instances must have the same or later versions and as much as or more storage space than the original ones.
        • Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.
        • The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.
        • Time points that data can be restored to depend on the backup policy set on original data nodes.
        -

        Procedure

        1. Log in to the DDM console.
        2. Create a new DDM instance in the region where the source DDM instance is located or select an existing DDM instance that meets the requirements.

          Ensure that the new DDM instance or the selected existing DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.

          +
          • Restoring data to a new DDM instance will overwrite data on it and cause the instance to be unavailable during restoration.
          • The new RDS for MySQL instances must have the same or later versions and as much as or more storage space than the original ones.
          • Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.
          • The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.
          • Time points that data can be restored to depend on the backup policy set on original data nodes.
          +

          Procedure

          1. Log in to the DDM console.
          2. Create a new DDM instance in the region where the source DDM instance is located or select an existing DDM instance that meets the requirements.

            Ensure that the new DDM instance or the selected existing DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.

            -

          3. On the RDS console, create as many RDS for MySQL instances as there are in the source DDM instance.

            • Ensure that the new RDS instances have the same or later versions than RDS instances associated with the source DDM instance.
            • Ensure that each new RDS for MySQL instance has the same or larger storage space than each source RDS instance.
            +

          4. On the RDS console, create as many RDS for MySQL instances as there are in the source DDM instance.

            • Ensure that the new RDS instances have the same or later versions than RDS instances associated with the source DDM instance.
            • Ensure that each new RDS for MySQL instance has the same or larger storage space than each source RDS instance.
            -

          5. Switch back to the DDM console, in the instance list, locate the DDM instance whose data you want to restore, and click its name.
          6. In the navigation pane on the left, choose Backups & Restorations.
          7. Click Restore to New Instance.
          8. On the displayed Restore to New Instance page, specify a time range and a point in time, and select destination DDM instance and associated data nodes.

            -

            Table 1 Parameter description

            Parameter

            +

          9. Switch back to the DDM console, in the instance list, locate the DDM instance whose data you want to restore, and click its name.
          10. In the navigation pane on the left, choose Backups & Restorations.
          11. Click Restore to New Instance.
          12. On the displayed Restore to New Instance page, specify a time range and a point in time, and select destination DDM instance and associated data nodes.

            +

            - - - - - - - - -
            Table 1 Parameter description

            Parameter

            Description

            +

            Description

            Time Range

            +

            Time Range

            Select a time range.

            +

            Select a time range.

            Time Point

            +

            Time Point

            Select a time point.

            -

            DDM checks whether the associated data nodes have available backups at the selected point in time.

            +

            Select a time point.

            +

            DDM checks whether the associated data nodes have available backups at the selected point in time.

            Destination DDM Instance

            +

            Destination DDM Instance

            Select the DDM instance created in 2 as the destination instance.

            +

            Select the DDM instance created in 2 as the destination instance.

            Associated Data Nodes

            +

            Associated Data Nodes

            Select the RDS for MySQL instances created in 3 as the destination data nodes.

            +

            Select the RDS for MySQL instances created in 3 as the destination data nodes.
            -

          13. Confirm the information and click OK. Wait for 1 to 3 minutes for the data restoration to complete.
            14. +

          14. Confirm the information and click OK. Wait for 1 to 3 minutes for the data restoration to complete.
            15. diff --git a/docs/ddm/umn/ddm_06_0017.html b/docs/ddm/umn/ddm_06_0017.html new file mode 100644 index 00000000..3590da22 --- /dev/null +++ b/docs/ddm/umn/ddm_06_0017.html @@ -0,0 +1,73 @@ + + +

            Restoring Metadata

            +

            DDM automatically backs up DDM instance metadata at 02:00 UTC+00:00 every day and retains the backup data for 30 days. Metadata backup is also triggered by key operations, such as deleting a schema, deleting data after shard configuration, and deleting instances.

            +

            When you delete a schema by mistake or your RDS for MySQL instances become abnormal, metadata restoration allows you to restore your DDM instance metadata and match the metadata with the RDS instance that has completed PITR to re-establish the relationship between your DDM instance and RDS instance. Metadata restoration supports only RDS for MySQL.

            +

            To restore metadata of a DDM instance, you can specify a point in time by referring to Restoring Metadata to a Point in Time, or using an available backup by referring to Restoring Metadata Using Backups.

            +

            Metadata restoration mainly restores the metadata of your DDM instance to a new DDM instance. It starts after a point-in-time recovery (PITR) for the associated data nodes is complete.

            +

            Prerequisites

            • There is a source DDM instance available and associated with an RDS for MySQL instance. This DB instance is the source data node.
            • The source data node has been restored to a specified time point.
            +
            +

            Constraints

            • The destination DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.
            • Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.
            • The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.
            • Time points that data can be restored to depend on the backup policy set on original data nodes.
            +
            +

            Restoring Metadata to a Point in Time

            1. Log in to the DDM console.
            2. Create a new DDM instance and use it as the destination DDM instance. For details, seeCreating a DDM Instance.
            3. In the DDM instance list, locate the source instance and click its name.
            4. In the navigation pane on the left, choose Backups & Restorations.
            5. Click Restore Metadata.
            6. On the displayed page, specify a time point. The source DDM instance will select an appropriate DDM metadata backup closest to the time point.

              +

              + + + + + + + + + + + + + +
              Table 1 Parameter description

              Parameter

              +

              Description

              +

              Restore To

              +

              Specify a point in time. DDM will restore metadata to this point in time using the most recent backup.

              +

              Destination DDM Instance

              +

              Select the DDM instance created in 2.

              +

              Destination Data Nodes

              +

              Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.

              +
              +
              +

            7. Click OK. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.
            +
            +

            Restoring Metadata Using Backups

            1. Log in to the DDM console.
            2. Create a new DDM instance and use it as the destination DDM instance. For details, seeCreating a DDM Instance.
            3. In the DDM instance list, locate the source instance and click its name.
            4. In the navigation pane on the left, choose Backups.
            5. Locate the required backup based on the instance name and backup time and click Restore in the Operation column.

              +

            6. On the displayed page, configure required parameters.

              +

              + + + + + + + + + + + + + +
              Table 2 Parameter description

              Parameter

              +

              Description

              +

              Backup Name

              +

              Name of the backup to be restored.

              +

              Destination DDM Instance

              +

              Select the DDM instance created in 2.

              +

              Destination Data Nodes

              +

              Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.

              +
              +
              +

            7. Click OK. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.
            +
            +
            +
            +
            +
            Parent topic: Backups and Restorations
            +
            +
            + diff --git a/docs/ddm/umn/ddm_06_0132.html b/docs/ddm/umn/ddm_06_0132.html new file mode 100644 index 00000000..14b6381c --- /dev/null +++ b/docs/ddm/umn/ddm_06_0132.html @@ -0,0 +1,94 @@ + + +

            Creating a DDM Instance

            +

            Prerequisites

            You have logged in to the DDM console.

            +
            +

            Procedure

            1. On the displayed page, in the upper right corner, click Create DDM Instance.
            2. On the displayed page, configure the required parameters.

              +

              + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
              Table 1 Parameter description

              Parameter

              +

              Description

              +

              Region

              +

              Region where the DDM instance is located. Select the required region.

              +

              AZ

              +

              Availability zone where the DDM instance is deployed.

              +

              Nodes in a DDM instance can be deployed on different physical servers in the same AZ to keep services always available even if one physical server becomes faulty.

              +

              A DDM instance can be deployed across AZs to provide cross-AZ DR.

              +

              If necessary, you can select multiple AZs when you create a DDM instance. Then nodes of the instance will be deployed in multiple different AZs.

              +
              NOTE:

              Deploy your application, DDM instance, and required RDS instances in the same AZ to reduce network latency. Cross-AZ deployment may increase network latency.

              +
              +

              Instance Name

              +

              Name of the DDM instance, which:

              +
              • Cannot be left blank.
              • Must start with a letter.
              • Must be 4 to 64 characters long.
              • Can contain only letters, digits, and hyphens (-).
              +

              Node Class

              +

              Class of the DDM instance node. You can select General-enhanced or Kunpeng general computing-plus and then specify a node class.

              +
              NOTE:

              Estimate compute and storage requirements of your applications based on your service type and scale before you create a DDM instance, and then select an appropriate node class so that the CPU and memory specifications of your DDM instance can better meet your needs.

              +
              +

              Instance Nodes

              +

              Number of nodes in a DDM instance. Up to 32 nodes are supported.

              +
              NOTE:

              At least 2 nodes are recommended because using a single node cannot guarantee high availability.

              +
              +

              VPC

              +

              VPC that the DDM instance belongs to. This VPC isolates networks for different services. It allows you to manage and configure private networks, simplifying network management.

              +

              Click View VPC to show more details and security group rules.

              +
              NOTE:

              The DDM instance should be in the same VPC as the required RDS for MySQL instance.

              +

              To ensure network connectivity, the DDM instance you purchased must be in the same VPC as your applications and RDS for MySQL instances.

              +
              +

              Subnet

              +

              Name and IP address range of the subnet

              +

              Security Group

              +

              Select an existing security group.

              +

              You are advised to select the same security group for your DDM instance, application, and RDS for MySQL instances so that they can communicate with each other. If different security groups are selected, add security group rules to enable network access.

              +

              Parameter Template

              +

              Select an existing parameter template. You can also click View Parameter Template to set parameters on the displayed page.

              +

              Tags

              +

              (Optional) Adding tags helps you better identify and manage your DDM resources.

              +

              You can add tags to your instance. Each instance can have a maximum of 20 tags.

              +

              Tag key: This parameter is mandatory and cannot be null.

              +
              • Must be unique for each instance.
              • Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
              • Can include 1 to 36 characters.
              • Cannot be an empty string or start with _sys_.
              +
              Tag value: This parameter is mandatory.
              • Is an empty string by default.
              • Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
              • Can contain 0 to 43 characters.
              +
              +
              +
              +

            3. After the configuration is complete, click Create Now at the bottom of the page.
            4. Confirm the configurations and click Submit.
            +
            +
            +
            +
            +
            Parent topic: Instance Management
            +
            +
            + diff --git a/docs/ddm/umn/ddm-08-0001.html b/docs/ddm/umn/ddm_08_0001.html similarity index 70% rename from docs/ddm/umn/ddm-08-0001.html rename to docs/ddm/umn/ddm_08_0001.html index cf6f493f..24769355 100644 --- a/docs/ddm/umn/ddm-08-0001.html +++ b/docs/ddm/umn/ddm_08_0001.html @@ -1,4 +1,4 @@ - +

            SQL Syntax

            @@ -6,15 +6,15 @@
            -
            Parent topic: SQL Syntax
            +
            Parent topic: SQL Syntax
            diff --git a/docs/ddm/umn/ddm_08_0004.html b/docs/ddm/umn/ddm_08_0004.html new file mode 100644 index 00000000..1ca7c07d --- /dev/null +++ b/docs/ddm/umn/ddm_08_0004.html @@ -0,0 +1,31 @@ + + +

            DML

            +
            + + diff --git a/docs/ddm/umn/ddm-08-0005.html b/docs/ddm/umn/ddm_08_0005.html similarity index 53% rename from docs/ddm/umn/ddm-08-0005.html rename to docs/ddm/umn/ddm_08_0005.html index e9574137..9f1a3e78 100644 --- a/docs/ddm/umn/ddm-08-0005.html +++ b/docs/ddm/umn/ddm_08_0005.html @@ -1,8 +1,8 @@ - +

            INSERT

            -

            INSERT is used to insert data into database objects.

            -

            Common Syntax

            INSERT [INTO] tbl_name
+
            INSERT is used to insert data into database objects.
            
+
            Common Syntax
            INSERT [INTO] tbl_name
 [(col_name,...)]
 {VALUES | VALUE} ({expr },...),(...),...
 [ ON DUPLICATE KEY UPDATE
@@ -14,14 +14,14 @@ SET col_name={expr | DEFAULT}, ...
 [ ON DUPLICATE KEY UPDATE
 col_name=expr [, col_name=expr] ... ]
            
 
            
-
            Syntax Restrictions
            • INSERT DELAYED is not supported.
            • Only INSERT statements that contain sharding fields are supported.
            • PARTITION syntax is not supported. Partitioned tables are not recommended.
            • Setting datetime to 1582 or any value smaller in INSERT statements is not supported.
            • INSERT cannot be used to insert sharding key value DEFAULT.
            • If you specify an auto-increment key value in an INSERT statement and execute it on a sharded table, the auto-increment key value of the inserted data entry changes. Auto-increment key values of data entries inserted subsequently will increase based on the first inserted data entry unless you specify a new auto-increment key value.
            • Referencing a table column in function REPEAT of the VALUES statement is not supported, for example, INSERT INTO T(NAME) VALUES(REPEAT(ID,3)).
            
+
            Syntax Restrictions
            • INSERT DELAYED is not supported.
            • Only INSERT statements that contain sharding fields are supported.
            • PARTITION syntax is not supported. Partitioned tables are not recommended.
            • Setting datetime to 1582 or any value smaller in INSERT statements is not supported.
            • INSERT cannot be used to insert sharding key value DEFAULT.
            • If you specify an auto-increment key value in an INSERT statement and execute it on a sharded table, the auto-increment key value of the inserted data entry changes. Auto-increment key values of data entries inserted subsequently will increase based on the first inserted data entry unless you specify a new auto-increment key value.
            • Referencing a table column in function REPEAT of the VALUES statement is not supported, for example, INSERT INTO T(NAME) VALUES(REPEAT(ID,3)).
            
 
            
-
            Use Constraints
            • If the sharding key value in the INSERT statement is invalid, data is routed to database shard 0 or table shard 0 by default.
            • Do not use functions VERSION, DATABASE, or USER in the INSERT statement. When you execute such as functions, you may not obtain the expected results because its results depend on whether it pushed to data nodes for execution.
            
+
            Use Constraints
            • If the sharding key value in the INSERT statement is invalid, data is routed to database shard 0 or table shard 0 by default.
            • Do not use functions VERSION, DATABASE, or USER in the INSERT statement. When you execute such as functions, you may not obtain the expected results because its results depend on whether it pushed to data nodes for execution.
            
 
            
 
            
 
            
 
            
-
            Parent topic: DML
            
+
            Parent topic: DML
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm-08-0006.html b/docs/ddm/umn/ddm_08_0006.html
similarity index 54%
rename from docs/ddm/umn/ddm-08-0006.html
rename to docs/ddm/umn/ddm_08_0006.html
index 88cdd35e..5d318f7c 100644
--- a/docs/ddm/umn/ddm-08-0006.html
+++ b/docs/ddm/umn/ddm_08_0006.html
@@ -1,8 +1,8 @@
-
+
 
 
            SELECT
            
-
            SELECT is generally used to query data in one or more tables.
            
-
            Common Syntax
            SELECT
+
            SELECT is generally used to query data in one or more tables.
            
+
            Common Syntax
            SELECT
 [ALL | DISTINCT | DISTINCTROW ]
 select_expr
 [, select_expr ...]
@@ -11,54 +11,54 @@ select_expr
 [HAVING where_condition] [ORDER BY {col_name | expr | position} [ASC | DESC], ...]
 [LIMIT {[offset,] row_count | row_count OFFSET offset}]
            
 
            
-
            
-
            Table 1 Supported syntax
            Syntax
            
+
            
+
            
-
-
-
-
-
-
-
-
-
-
-
-
-
            Table 1 Supported syntax
            Syntax
            
 
            Description
            
+
            Description
            
             		
 
            
 
            select_expr
            
+
            select_expr
            
 
            Indicates a column that you want to query.
            
+
            Indicates a column that you want to query.
            
             		
 
            FROM table_references
            
+
            FROM table_references
            
 
            Indicates the tables that you want to query.
            
+
            Indicates the tables that you want to query.
            
             		
 
            WHERE
            
+
            WHERE
            
 
            Followed by an expression to filter for rows that meet certain criteria.
            
+
            Followed by an expression to filter for rows that meet certain criteria.
            
             		
 
            GROUP BY
            
+
            GROUP BY
            
 
            Groups the clauses used in SQL in sequence. GROUP BY indicates relationships between statements and supports column names. For example, the HAVING clause must be after the GROUP BY clause and before the ORDER BY clause.
            
+
            Groups the clauses used in SQL in sequence. GROUP BY indicates relationships between statements and supports column names. For example, the HAVING clause must be after the GROUP BY clause and before the ORDER BY clause.
            
             		
 
            ORDER BY
            
+
            ORDER BY
            
 
            Indicates relationships between statements. Sorting by column name or by a specified order such as ASC and DESC is supported.
            
+
            Indicates relationships between statements. Sorting by column name or by a specified order such as ASC and DESC is supported.
            
             		
 
            LIMIT/OFFSET
            
+
            LIMIT/OFFSET
            
 
            Restrains the offset and size of output result sets, for example, one or two values can be input after LIMIT.
            
+
            Restrains the offset and size of output result sets, for example, one or two values can be input after LIMIT.
            
             		
 
            
             
 
            
 
            
 
            
-
            Syntax Description
            • An empty string cannot be used as an alias.
            • The SELECT... GROUP BY... WITH ROLLUP QUERY statement is not supported. (When the queried table is a sharded table, you cannot obtain the expected result)
            • Neither STRAIGHT_JOIN nor NATURAL JOIN is supported.
            • The SELECT FOR UPDATE statement supports only simple queries and does not support JOIN, GROUP BY, ORDER BY, or LIMIT.
            • Each SELECT statement in UNION does not support multiple columns with the same name, for example,
              SELECT id, id, name FROM t1 UNION SELECT pk, pk, name FROM t2 is not supported because this statement has duplicate column names.
              
-
            • User-defined sequencing similar to ORDER BY FIELD(id,1,2,3) is not supported.
            
+
            Syntax Description
            • An empty string cannot be used as an alias.
            • The SELECT... GROUP BY... WITH ROLLUP QUERY statement is not supported. (When the queried table is a sharded table, you cannot obtain the expected result)
            • Neither STRAIGHT_JOIN nor NATURAL JOIN is supported.
            • The SELECT FOR UPDATE statement supports only simple queries and does not support JOIN, GROUP BY, ORDER BY, or LIMIT.
            • Each SELECT statement in UNION does not support multiple columns with the same name, for example,
              SELECT id, id, name FROM t1 UNION SELECT pk, pk, name FROM t2 is not supported because this statement has duplicate column names.
              
+
            • User-defined sequencing similar to ORDER BY FIELD(id,1,2,3) is not supported.
            
 
            
 
            
 
            
 
            
-
            Parent topic: DML
            
+
            Parent topic: DML
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm-08-0007.html b/docs/ddm/umn/ddm_08_0007.html
similarity index 50%
rename from docs/ddm/umn/ddm-08-0007.html
rename to docs/ddm/umn/ddm_08_0007.html
index 075d3ea2..e39b7fe9 100644
--- a/docs/ddm/umn/ddm-08-0007.html
+++ b/docs/ddm/umn/ddm_08_0007.html
@@ -1,18 +1,18 @@
-
+
 
 
            REPLACE
            
-
            REPLACE is used to insert rows into or replace rows in a table.
            
-
            Common Syntax
            replace into table(col1,col2,col3)
+
            REPLACE is used to insert rows into or replace rows in a table.
            
+
            Common Syntax
            replace into table(col1,col2,col3)
 values(value1,value2,value3)
            
 
            
-
            Syntax Constraints
            • PARTITION syntax is not supported.
            • If an auto-increment table has no ID, you can insert a data record with a specified ID using REPLACE, but no ID is generated.
            
+
            Syntax Constraints
            • PARTITION syntax is not supported.
            • If an auto-increment table has no ID, you can insert a data record with a specified ID using REPLACE, but no ID is generated.
            
 
            
-
            Use Constraints
            • If the sharding key value in the REPLACE statement is invalid, data is routed to database shard 0 or table shard 0 by default.
            • Do not use functions VERSION, DATABASE, or USER in the REPLACE statement. When you execute such as functions, you may not obtain the expected results because its results depend on whether it pushed to data nodes for execution.
            
+
            Use Constraints
            • If the sharding key value in the REPLACE statement is invalid, data is routed to database shard 0 or table shard 0 by default.
            • Do not use functions VERSION, DATABASE, or USER in the REPLACE statement. When you execute such as functions, you may not obtain the expected results because its results depend on whether it pushed to data nodes for execution.
            
 
            
 
            
 
            
 
            
-
            Parent topic: DML
            
+
            Parent topic: DML
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_08_0008.html b/docs/ddm/umn/ddm_08_0008.html
new file mode 100644
index 00000000..75c03177
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0008.html
@@ -0,0 +1,16 @@
+
+
+
            DELETE
            
+
            DELETE is used to delete rows that meet conditions from a table.
            
+
            Common Syntax
            DELETE [IGNORE]
+FROM tbl_name [WHERE where_condition]
            
+
            
+
            Syntax Restrictions
            • The WHERE clause does not support subqueries, including correlated and non-correlated subqueries.
            • Data in reference tables cannot be deleted when multiple tables are deleted at a time.
            • PARTITION clauses are not supported.
            
+
            
+
            
+
            
+
            
+
            Parent topic: DML
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_08_0009.html b/docs/ddm/umn/ddm_08_0009.html
new file mode 100644
index 00000000..f2d004ca
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0009.html
@@ -0,0 +1,17 @@
+
+
+
            UPDATE
            
+
            Common Syntax
            UPDATE table_reference
+SET col_name1={expr1} [, col_name2={expr2}] ...
+[WHERE where_condition]
            
+
            
+
            Syntax Restrictions
            • Subqueries are not supported, including correlated and non-correlated subqueries.
            • Cross-shard subquery is not supported.
            • The WHERE condition in the UPDATE statement does not support arithmetic expressions and their subqueries.
            • Modifying broadcast tables is not supported during an update of multiple tables. (Data in columns of a broadcast table cannot be on the left of SET assignment statements).
            • Updating the sharding key field of a logical table is not supported because this operation may cause data redistribution.
            • Setting datetime to 1582 or any value smaller in UPDATE statements is not supported.
            • UPDATE cannot be used to update sharding key value DEFAULT.
            • Repeatedly updating the same field in an UPDATE statement is not supported.
            • Updating a sharding key using UPDATE JOIN syntax is not supported.
            • UPDATE cannot be used to update self-joins.
            • Referencing other object columns in assignment statements or expressions may cause unexpected update results. Example:
              update tbl_1 a,tbl_2 b set a.name=concat(b.name,'aaaa'),b.name=concat(a.name,'bbbb') on a.id=b.id
              
+
            • UPDATE JOIN supports only joins with WHERE conditions.
            
+
            
+
            
+
            
+
            
+
            Parent topic: DML
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm-08-0010.html b/docs/ddm/umn/ddm_08_0010.html
similarity index 51%
rename from docs/ddm/umn/ddm-08-0010.html
rename to docs/ddm/umn/ddm_08_0010.html
index c8310be3..baf3f612 100644
--- a/docs/ddm/umn/ddm-08-0010.html
+++ b/docs/ddm/umn/ddm_08_0010.html
@@ -1,25 +1,25 @@
-
+
 
 
            SELECT JOIN Syntax
            
-
            Common Syntax
            table_references:
            
-
            table_reference [, table_reference] ...
            
-
            table_reference:
            
-
            table_factor | join_table
            
-
            table_factor:
            
-
            tbl_name [[AS] alias]
+
            Common Syntax
            table_references:
            
+
            table_reference [, table_reference] ...
            
+
            table_reference:
            
+
            table_factor | join_table
            
+
            table_factor:
            
+
            tbl_name [[AS] alias]
 | table_subquery [AS] alias
 | ( table_references )
            
-
            join_table:
            
-
            table_reference [INNER | CROSS] JOIN table_factor [join_condition]
+
            join_table:
            
+
            table_reference [INNER | CROSS] JOIN table_factor [join_condition]
 | table_reference {LEFT|RIGHT} [OUTER] JOIN table_reference join_condition
 | table_reference [{LEFT|RIGHT} [OUTER]] JOIN table_factor
            
-
            join_condition:
            
-
            ON conditional_expr
+
            join_condition:
            
+
            ON conditional_expr
 | USING (column_list)
            
 
            
-
            Syntax Restrictions
            SELECT STRAIGHT_JOIN and NATURAL JOIN are not supported.
            
+
            Syntax Restrictions
            SELECT STRAIGHT_JOIN and NATURAL JOIN are not supported.
            
 
            
-
            Example
            select id,name from test1 where id=1;
+
            Example
            select id,name from test1 where id=1;
 select distinct id,name from test1 where id>=1;
 select id,name from test1 order by id limit 2 offset 2;
 select id,name from test1 order by id limit 2,2;
@@ -30,7 +30,7 @@ select abs(sum(id)) from test1;
            
 
            
 
            
 
            
-
            Parent topic: DML
            
+
            Parent topic: DML
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm-08-0011.html b/docs/ddm/umn/ddm_08_0011.html
similarity index 57%
rename from docs/ddm/umn/ddm-08-0011.html
rename to docs/ddm/umn/ddm_08_0011.html
index 5a46c885..d4afa7fd 100644
--- a/docs/ddm/umn/ddm-08-0011.html
+++ b/docs/ddm/umn/ddm_08_0011.html
@@ -1,18 +1,18 @@
-
+
 
 
            SELECT UNION Syntax
            
-
            Common Syntax
            SELECT ...UNION [ALL | DISTINCT] 
+
            Common Syntax
            SELECT ...UNION [ALL | DISTINCT] 
 SELECT ...[UNION [ALL | DISTINCT] SELECT ...]
            
 
            
-
            Example
            select userid from user union select orderid from ordertbl order by userid;
+
            Example
            select userid from user union select orderid from ordertbl order by userid;
 select userid from user union (select orderid from ordertbl group by orderid) order by userid;
            
 
            
-
            Syntax Restrictions
            SELECT statements in UNION do not support duplicate column names.
            
+
            Syntax Restrictions
            SELECT statements in UNION do not support duplicate column names.
            
 
            
 
            
 
            
 
            
-
            Parent topic: DML
            
+
            Parent topic: DML
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm-08-0012.html b/docs/ddm/umn/ddm_08_0012.html
similarity index 56%
rename from docs/ddm/umn/ddm-08-0012.html
rename to docs/ddm/umn/ddm_08_0012.html
index af471a47..98bc4ab6 100644
--- a/docs/ddm/umn/ddm-08-0012.html
+++ b/docs/ddm/umn/ddm_08_0012.html
@@ -1,21 +1,21 @@
-
+
 
 
            SELECT Subquery Syntax
            
-
            Subquery as Scalar Operand
            Example
            
-
            SELECT (SELECT id FROM test1 where id=1);         
+
            Subquery as Scalar Operand
            Example
            
+
            SELECT (SELECT id FROM test1 where id=1);         
 SELECT (SELECT id FROM test2 where id=1)FROM test1;              
 SELECT UPPER((SELECT name FROM test1 limit 1)) FROM test2;
            
 
            
-
            Comparisons Using Subqueries
            Syntax
            
-
            non_subquery_operand comparison_operator (subquery)
+
            Comparisons Using Subqueries
            Syntax
            
+
            non_subquery_operand comparison_operator (subquery)
 comparison_operator: = > < >= <= <> != <=> like
            
 
            
-
            Example
            
-
            select name from test1 where id > (select id from test2 where id=1);
+
            Example
            
+
            select name from test1 where id > (select id from test2 where id=1);
 select name from test1 where id = (select id from test2 where id=1);
 select id from test1 where name like (select name from test2 where id=1);
            
-
            Subqueries with ANY, IN, NOT IN, SOME,ALL,Exists,NOT Exists
            Syntax
            
-
            operand comparison_operator SOME (subquery)
+
            Subqueries with ANY, IN, NOT IN, SOME,ALL,Exists,NOT Exists
            Syntax
            
+
            operand comparison_operator SOME (subquery)
 operand comparison_operator ALL (subquery)
 operand comparison_operator ANY (subquery) 
 operand IN (subquery) 
@@ -23,26 +23,26 @@ operand not IN (subquery)
 operand exists (subquery)
 operand not exists (subquery)
            
 
            
-
            Example
            
-
            select id from test1 where id > any (select id from test2);
+
            Example
            
+
            select id from test1 where id > any (select id from test2);
 select id from test1 where id > some (select id from test2);
 select id from test1 where id > all (select id from test2);
 select id from test1 where id in (select id from test2);
 select id from test1 where id not in (select id from test2);
 select id from test1 where exists (select id from test2 where id=1);
 select id from test1 where not exists (select id from test2 where id=1);
            
-
            Derived Tables (Subqueries in the FROM Clause)
            Syntax
            
-
            SELECT ... FROM (subquery) [AS] tbl_name ...
            
-
            Example
            
-
            select id from (select id,name from test2 where id>1) a  order by a.id;
            
+
            Derived Tables (Subqueries in the FROM Clause)
            Syntax
            
+
            SELECT ... FROM (subquery) [AS] tbl_name ...
            
+
            Example
            
+
            select id from (select id,name from test2 where id>1) a  order by a.id;
            
 
            
-
            Syntax Restrictions
            • Each derived table must have an alias.
            • A derived table cannot be a correlated subquery.
            • In some cases, correct results cannot be obtained using a scalar subquery. Using JOIN instead is recommended to improve query performance.
            • Using subqueries in the HAVING clause and the JOIN ON condition is not supported.
            
-
            • Row subqueries are not supported.
            
+
            Syntax Restrictions
            • Each derived table must have an alias.
            • A derived table cannot be a correlated subquery.
            • In some cases, correct results cannot be obtained using a scalar subquery. Using JOIN instead is recommended to improve query performance.
            • Using subqueries in the HAVING clause and the JOIN ON condition is not supported.
            
+
            • Row subqueries are not supported.
            
 
            
 
            
 
            
 
            
-
            Parent topic: DML
            
+
            Parent topic: DML
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_08_0013.html b/docs/ddm/umn/ddm_08_0013.html
new file mode 100644
index 00000000..f96153f6
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0013.html
@@ -0,0 +1,16 @@
+
+
+
            Use Constraints
            
+
            DDM is compatible with the MySQL license and syntax, but the use of SQL statements is limited due to differences between distributed databases and single-node databases.
            
+
            Unsupported SQL Statements
            • Triggers
            • Temporary tables
            • DO statement
            • Association with foreign keys
            • RESET statement
            • FLUSH statement
            • BINLOG statement
            • HANDLER statement
            • SHOW WARNINGS statement
            • Assignment operator :=
            • Operators less than (<), assignment (=), and more than (>)
            • Expression IS UNKNOWN
            • INSTALL and UNINSTALL PLUGIN statements
            • Cross-shard stored procedures and custom functions
            • Statements for modifying database names, table names, and sharding field names and types
            • Most of SHOW statements such as SHOW PROFILES and SHOW ERRORS
            • Table maintenance statements, including ANALYZE, CHECK, CHECKSUM, OPTIMIZE, and REPAIR TABLE
            • Statements for assigning a value to or querying variable session, for example, set @rowid=0;select @rowid:=@rowid+1,id from user
            • SQL statements that use -- or /*...*/ to comment out a single line or multiple lines of code
            • The result of the REPEAT function contains a maximum of 1,000,000 characters (in version 3.0.9 or later).
            
+
            
+
            Permission Levels
            Permission levels supported by DDM are as follows:
            
+
            • Global level (not supported)
            • Database level (supported)
            • Table level (supported)
            • Column level (not supported)
            • Subprogram level (not supported)
            • User level (supported)
            
+
            
+
            
+
            
+
            
+
            Parent topic: SQL Syntax
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm-08-0014.html b/docs/ddm/umn/ddm_08_0014.html
similarity index 62%
rename from docs/ddm/umn/ddm-08-0014.html
rename to docs/ddm/umn/ddm_08_0014.html
index 4f4224f9..a3711804 100644
--- a/docs/ddm/umn/ddm-08-0014.html
+++ b/docs/ddm/umn/ddm_08_0014.html
@@ -1,17 +1,17 @@
-
+
 
 
            CHECK TABLE
            
 
            
 
 
diff --git a/docs/ddm/umn/ddm_08_0015.html b/docs/ddm/umn/ddm_08_0015.html
new file mode 100644
index 00000000..7e280c83
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0015.html
@@ -0,0 +1,32 @@
+
+
+
            SHOW RULE
            
+
            Command Format 1:
            
+
            show rule;
            
+
            It is used to view the sharding rule of each logical table in a certain schema.
            
+
            Command output:
            
+
            
+
            Command Format 2:
            
+
            show rule from <table_name>;
            
+
            It is used to view the sharding rule of a specific logical table in a certain schema.
            
+
            Command output:
            
+
            
+
            Output Details:
            
+
            TABLE_NAME: indicates the name of the logical table.
            
+
            BROADCAST: specifies whether the table is a broadcast table. 0 indicates that the table is not a broadcast table. 1 indicates the table is a broadcast table.
            
+
            DB_PARTITION_KEY: indicates the database sharding key. Leave this field blank if database sharding is not required.
            
+
            DB_PARTITION_POLICY: indicates the database sharding algorithm. The value can be HASH, YYYYMM, YYYYDD, and YYYYWEEK.
            
+
            DB_PARTITION_COUNT: indicates the number of database shards.
            
+
            DB_PARTITION_OFFSET: indicates where a new database shard starts from.
            
+
            PARTITION_RANGE: indicates the sharding range when the database sharding algorithm is range.
            
+
            TB_PARTITION_KEY: indicates the table sharding key. Leave this field blank if table sharding is not required.
            
+
            TB_PARTITION_POLICY: indicates the table sharding algorithm. The value can be HASH, MM, DD, MMDD, or WEEK.
            
+
            TB_PARTITION_COUNT: indicates the number of physical tables in each database shard.
            
+
            TB_PARTITION_OFFSET: indicates where a new physical table starts from.
            
+
            
+
            
+
            
+
            Parent topic: Supported SQL Statements
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_08_0017.html b/docs/ddm/umn/ddm_08_0017.html
new file mode 100644
index 00000000..0bb6d80c
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0017.html
@@ -0,0 +1,20 @@
+
+
+
            SHOW TOPOLOGY
            
+
            Command Format:
            
+
            show topology from <table_name>;
            
+
            It is used to view physical tables corresponding to a specified logical table.
            
+
            Output Details:
            
+
            RDS_instance_id: indicates the ID of the RDS instance.
            
+
            HOST: indicates the IP address of the RDS instance.
            
+
            PORT: indicates the port number of the RDS instance.
            
+
            DATABASE: indicates the physical database in the RDS instance.
            
+
            TABLE: indicates the physical table.
            
+
            ROW_COUNT: indicates the estimated number of data entries in each physical table. The value is obtained from information_schema.TABLES.
            
+
            
+
            
+
            
+
            Parent topic: Supported SQL Statements
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_08_0021.html b/docs/ddm/umn/ddm_08_0021.html
new file mode 100644
index 00000000..a3949df9
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0021.html
@@ -0,0 +1,22 @@
+
+
+
            Checking DDL Consistency of Physical Tables in All Logical Tables
            
+
            Purpose: To check DDL consistency of all logical tables in one schema
            
+
            Command Format:
            
+
             check table
            
+
            Command Output:
            
+
            The following output is returned if DDL check results of all logical tables are consistent.
            
+
            
+
            The following output is returned if there are logical tables with inconsistent DDL check results.
            
+
            
+
            Output Details:
            
+
            Each row contains the check result of a logical table.
            
+
            • DATABASE_NAME: indicates the schema name.
            • TABLE_NAME: indicates the logical table name.
            • TABLE_TYPE: indicates the logical table type.
              • SINGLE: indicates that the logical table is unsharded.
              • BROADCAST: indicates that the table is a broadcast table.
              • SHARDING: indicates that the table is sharded.
              
+
            • DDL_CONSISTENCY: indicates whether DDL results of all physical tables corresponding to the logical table are consistent.
            • TOTAL_COUNT: indicates the number of physical tables in the logical table.
            • INCONSISTENT_COUNT: indicates the number of physical tables with inconsistent DDL results.
            • DETAILS: indicates names of the physical tables with inconsistent DDL check results.
            
+
            
+
            
+
            
+
            Parent topic: CHECK TABLE
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_08_0022.html b/docs/ddm/umn/ddm_08_0022.html
new file mode 100644
index 00000000..a135b2ca
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0022.html
@@ -0,0 +1,21 @@
+
+
+
            Checking DDL Consistency of Physical Tables in One Logical Table
            
+
            Purpose: To check DDL consistency of physical tables in a specific logical table
            
+
            Command Format:
            
+
            check table <table_name>
            
+
            Command Output:
            
+
            If the returned result set is empty, DDL results of physical tables in this logical table are consistent.
            
+
            
+
            If the returned result set is not empty, there are physical tables with inconsistent DDL results.
            
+
            
+
            Output Details:
            
+
            Each row displays details of a physical table with inconsistent DDL results.
            
+
            • DATABASE_NAME: indicates the database shard containing the physical table.
            • TABLE_NAME: indicates the name of the physical table.
            • TABLE_TYPE: indicates the type of the logical table that the physical table belongs to.
            • EXTRA_COLUMNS: indicates extra columns in the physical table.
            • MISSING_COLUMNS: indicates missing columns in the physical table.
            • DIFFERENT_COLUMNS: indicates name and type columns whose attributes are inconsistent in the physical table.
            • KEY_DIFF: indicates inconsistent indexes in the physical table.
            • ENGINE_DIFF: indicates inconsistent engines in the physical table.
            • CHARSET_DIFF: indicates inconsistent character sets in the physical table.
            • COLLATE_DIFF: indicates inconsistent collations in the physical table.
            • EXTRA_PARTITIONS: indicates extra partitions in the physical table. This field is only available to partitioned tables.
            • MISSING_PARTITIONS: indicates missing partitions in the physical table. This field is only available to partitioned tables.
            • DIFFERENT_PARTITIONS: indicates partitions with inconsistent attributes in the physical table. This field is only available to partitioned tables.
            • EXTRA_INFO: indicates other information such as missing physical tables.
            
+
            
+
            
+
            
+
            Parent topic: CHECK TABLE
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm-08-0023.html b/docs/ddm/umn/ddm_08_0023.html
similarity index 50%
rename from docs/ddm/umn/ddm-08-0023.html
rename to docs/ddm/umn/ddm_08_0023.html
index 1881dac7..a46ce39c 100644
--- a/docs/ddm/umn/ddm-08-0023.html
+++ b/docs/ddm/umn/ddm_08_0023.html
@@ -1,19 +1,19 @@
-
+
 
 
            TRUNCATE TABLE
            
 
            
 
 
diff --git a/docs/ddm/umn/ddm_08_0024.html b/docs/ddm/umn/ddm_08_0024.html
new file mode 100644
index 00000000..083cd8d0
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0024.html
@@ -0,0 +1,16 @@
+
+
+
            HINT-DB
            
+
            Command Format:
            
+
            /*+db=<physical_db_name>*/ TRUNCATE TABLE <table_name>
            
+
            Description:
            
+
            Deleting data in physical tables corresponding to <table_name> in <physical_db_name> does not affect physical tables in other database shards.
            
+
             
            HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way.
            
+
            
+
            
+
            
+
            
+
            Parent topic: TRUNCATE TABLE
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_08_0025.html b/docs/ddm/umn/ddm_08_0025.html
new file mode 100644
index 00000000..57484bd9
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0025.html
@@ -0,0 +1,21 @@
+
+
+
            HINT-TABLE
            
+
            HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way. This section describes how to use HINT syntax to delete data from a table.
            
+
            Command Format:
            
+
            /*+table=<physical_table_name>*/ TRUNCATE TABLE <table_name>
            
+
            Description:
            
+
            Deleting data in physical table <physical_table_name> in the current database shard does not affect other physical tables.
            
+
            Example output before the table is deleted:
            
+
            
+
            Example output after the table is deleted:
            
+
            
+
             
            Hints are valid only for sharded tables.
            
+
            
+
            
+
            
+
            
+
            Parent topic: TRUNCATE TABLE
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_08_0026.html b/docs/ddm/umn/ddm_08_0026.html
new file mode 100644
index 00000000..ba8dcf3d
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0026.html
@@ -0,0 +1,16 @@
+
+
+
            HINT-DB/TABLE
            
+
            Command Format:
            
+
            /*+db=<physical_db_name>,table=<physical_table_name>*/ TRUNCATE TABLE <table_name>
            
+
            Description:
            
+
            Deleting data in physical table <physical_table_name> in database shard <physical_db_name> does not affect other physical tables.
            
+
             
            Hints are valid only for sharded tables.
            
+
            
+
            
+
            
+
            
+
            Parent topic: TRUNCATE TABLE
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm-08-0027.html b/docs/ddm/umn/ddm_08_0027.html
similarity index 51%
rename from docs/ddm/umn/ddm-08-0027.html
rename to docs/ddm/umn/ddm_08_0027.html
index 4202eb90..ebb02aca 100644
--- a/docs/ddm/umn/ddm-08-0027.html
+++ b/docs/ddm/umn/ddm_08_0027.html
@@ -1,16 +1,16 @@
-
+
 
 
            HINT- ALLOW_ALTER_RERUN
            
-
            Command Format:
            
-
            /*+ allow_alter_rerun=true*/<ALTER TABLE>
            
-
            Description:
            
-
            Using this hint ensures that commands can be repeatedly executed, and no error is reported. This hint supports the following ALTER TABLE statements: ADD COLUMN, MODIFY COLUMN, DROP COLUMN, ADD INDEX, DROP INDEX, CHANGE COLUMN, ADD PARTITION, and DROP PARTITION.
            
-
            Example:
            
-
            /*+ allow_alter_rerun=true*/ALTER TABLE aaa_tb ADD schoolroll varchar(128)  not null comment 'Enrollment data'
            
+
            Command Format:
            
+
            /*+ allow_alter_rerun=true*/<ALTER TABLE>
            
+
            Description:
            
+
            Using this hint ensures that commands can be repeatedly executed, and no error is reported. This hint supports the following ALTER TABLE statements: ADD COLUMN, MODIFY COLUMN, DROP COLUMN, ADD INDEX, DROP INDEX, CHANGE COLUMN, ADD PARTITION, and DROP PARTITION.
            
+
            Example:
            
+
            /*+ allow_alter_rerun=true*/ALTER TABLE aaa_tb ADD schoolroll varchar(128)  not null comment 'Enrollment data'
            
 
            
 
            
 
            
-
            Parent topic: Supported SQL Statements
            
+
            Parent topic: Supported SQL Statements
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_08_0029.html b/docs/ddm/umn/ddm_08_0029.html
index f08c72f0..e51625b0 100644
--- a/docs/ddm/umn/ddm_08_0029.html
+++ b/docs/ddm/umn/ddm_08_0029.html
@@ -39,7 +39,7 @@ PRIMARY KEY(id)
 
            
 
            
 
            
-
            Parent topic: DDL
            
+
            Parent topic: DDL
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_08_0032.html b/docs/ddm/umn/ddm_08_0032.html
index 2b1d27a2..0ba9db04 100644
--- a/docs/ddm/umn/ddm_08_0032.html
+++ b/docs/ddm/umn/ddm_08_0032.html
@@ -26,7 +26,7 @@
 
            
 
            
 
            
-
            Parent topic: Supported SQL Statements
            
+
            Parent topic: Supported SQL Statements
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_08_0130.html b/docs/ddm/umn/ddm_08_0130.html
new file mode 100644
index 00000000..c4aa1f98
--- /dev/null
+++ b/docs/ddm/umn/ddm_08_0130.html
@@ -0,0 +1,18 @@
+
+
+
            SHOW DATA NODE
            
+
            Command Format:
            
+
            show data node;
            
+
            It is used to view data about database shards in the RDS instance.
            
+
            Output Details:
            
+
            RDS_instance_id: indicates the ID of the RDS instance.
            
+
            PHYSICAL_NODE: used to view physical databases in the RDS instance.
            
+
            HOST: indicates the IP address of the RDS instance.
            
+
            PORT: indicates the port number of the RDS instance.
            
+
            
+
            
+
            
+
            Parent topic: Supported SQL Statements
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_10_0018.html b/docs/ddm/umn/ddm_10_0018.html
index de90de32..3de6c557 100644
--- a/docs/ddm/umn/ddm_10_0018.html
+++ b/docs/ddm/umn/ddm_10_0018.html
@@ -31,7 +31,7 @@
 
 
 
            
-
            Parent topic: DDL
            
+
            Parent topic: DDL
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_12_0006.html b/docs/ddm/umn/ddm_12_0006.html
index 92438925..89596327 100644
--- a/docs/ddm/umn/ddm_12_0006.html
+++ b/docs/ddm/umn/ddm_12_0006.html
@@ -22,7 +22,7 @@
 
            
 
            
 
            
-
            Parent topic: DDL
            
+
            Parent topic: DDL
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_12_0100.html b/docs/ddm/umn/ddm_12_0100.html
index 9f20acf1..041102ea 100644
--- a/docs/ddm/umn/ddm_12_0100.html
+++ b/docs/ddm/umn/ddm_12_0100.html
@@ -24,7 +24,7 @@
 
            
 
            
 
            
-
            Parent topic: DML
            
+
            Parent topic: DML
            
 
            
 
            
 
diff --git a/docs/ddm/umn/ddm_history_0003.html b/docs/ddm/umn/ddm_history_0003.html
new file mode 100644
index 00000000..d01ddc50
--- /dev/null
+++ b/docs/ddm/umn/ddm_history_0003.html
@@ -0,0 +1,39 @@
+
+
+
            Change History
            
+
            
+
            
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
            Released On
            
+
            Description
            
+
            2024-03-14
            
+
            Optimized the prerequisites and procedures in Restoring Metadata.
            
+
            2023-12-15
            
+
            Optimized the description of tags in Tags.
            
+
            2023-10-20
            
+
            Modified the following content:
            
+
            Optimized the directory for monitoring management and the procedure for viewing monitoring information in Monitoring Management.
            
+
            Added parameter description in Restoring Metadata.
            
+
            Added the description of tags in Creating a DDM Instance.
            
+
            Added Tags.
            
+
            2023-01-30
            
+
            This is the first official release.
            
+
            
+
            
+
            
+
diff --git a/docs/ddm/umn/ddm_histroy_0003.html b/docs/ddm/umn/ddm_histroy_0003.html
deleted file mode 100644
index d110e1d0..00000000
--- a/docs/ddm/umn/ddm_histroy_0003.html
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
            Change History
            
-
            
-
            
-
-
-
-
-
-
-
-
-
-
-
-
-
-
            Released On
            
-
            Description
            
-
            2023-12-15
            
-
            Optimized the description of tags in Tags.
            
-
            2023-10-20
            
-
            Modified the following content:
            
-
            Optimized the directory for monitoring management and the procedure for viewing monitoring information in Monitoring Management.
            
-
            Added parameter description in Restoring Metadata.
            
-
            Added the description of tags in Creating a DDM Instance.
            
-
            Added Tags.
            
-
            2023-01-30
            
-
            This is the first official release.
            
-
            
-
            
-
            
-