Optimize modeling design scheme

Author: W1y1r

src/.vuepress/sidebar/V2.0.x/en-Tree.ts

@@ -188,6 +188,8 @@ export const enSidebar = {
       collapsible: true,
       prefix: 'SQL-Manual/',
       children: [
+        { text: 'Identifiers', link: 'Syntax-Rule' },
+        { text: 'Keywords', link: 'Keywords' },
         { text: 'SQL Manual', link: 'SQL-Manual' },
         {
           text: 'Functions and Operators',
@@ -236,14 +238,6 @@ export const enSidebar = {
             { text: 'DataNode Config Manual', link: 'DataNode-Config-Manual_apache' },
           ],
         },
-        {
-          text: 'Syntax-Rule',
-          collapsible: true,
-          children: [
-            { text: 'Identifiers', link: 'Syntax-Rule' },
-            { text: 'Keywords', link: 'Keywords' },
-          ],
-        },
         { text: 'Status Codes', link: 'Status-Codes' },
       ],
     },

src/UserGuide/Master/Tree/Basic-Concept/Operate-Metadata_apache.md

@@ -1011,7 +1011,59 @@ IoTDB> show timeseries where TAGS(tag1)='v1'
 
 The above operations are supported for timeseries tag, attribute updates, etc.
 
-## Node Management
+## Path query
+
+### Path
+
+A `path` is an expression that conforms to the following constraints:
+
+```sql
+path       
+    : nodeName ('.' nodeName)*
+    ;
+    
+nodeName
+    : wildcard? identifier wildcard?
+    | wildcard
+    ;
+    
+wildcard 
+    : '*' 
+    | '**'
+    ;
+```
+
+###  NodeName
+
+- The parts of a path separated by `.` are called node names (`nodeName`).
+- For example, `root.a.b.c` is a path with a depth of 4 levels, where `root`, `a`, `b`, and `c` are all node names.
+
+#### Constraints
+
+- **Reserved keyword `root`**: `root` is a reserved keyword that is only allowed at the beginning of a path. If `root` appears in any other level, the system will fail to parse it and report an error.
+- **Character support**: Except for the first level (`root`), other levels support the following characters:
+  - Letters (`a-z`, `A-Z`)
+  - Digits (`0-9`)
+  - Underscores (`_`)
+  - UNICODE Chinese characters (`\u2E80` to `\u9FFF`)
+- **Case sensitivity**: On Windows systems, path node names in the database are case-insensitive. For example, `root.ln` and `root.LN` are considered the same path.
+
+### Special Characters (Backquote)
+
+If special characters (such as spaces or punctuation marks) are needed in a `nodeName`, you can enclose the node name in Backquote (`). For more information on the use of backticks, please refer to [Backquote](../SQL-Manual/Syntax-Rule.md#reverse-quotation-marks).
+
+### Path Pattern
+
+To make it more convenient and efficient to express multiple time series, IoTDB provides paths with wildcards `*` and `**`. Wildcards can appear in any level of a path.
+
+- **Single-level wildcard (`\*`)**: Represents one level in a path.
+  - For example, `root.vehicle.*.sensor1` represents paths with a depth of 4 levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+- **Multi-level wildcard (`\**`)**: Represents one or more levels (`*`+).
+  - For example:
+    - `root.vehicle.device1.**` represents all paths with a depth of 4 or more levels, prefixed by `root.vehicle.device1`.
+    - `root.vehicle.**.sensor1` represents paths with a depth of 4 or more levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+
+**Note**: `*` and `**` cannot be placed at the beginning of a path.
 
 ### Show Child Paths
 

src/UserGuide/Master/Tree/Basic-Concept/Operate-Metadata_timecho.md

@@ -1052,7 +1052,59 @@ IoTDB> show timeseries where TAGS(tag1)='v1'
 
 The above operations are supported for timeseries tag, attribute updates, etc.
 
-## Node Management
+## Path query
+
+### Path
+
+A `path` is an expression that conforms to the following constraints:
+
+```sql
+path       
+    : nodeName ('.' nodeName)*
+    ;
+    
+nodeName
+    : wildcard? identifier wildcard?
+    | wildcard
+    ;
+    
+wildcard 
+    : '*' 
+    | '**'
+    ;
+```
+
+###  NodeName
+
+- The parts of a path separated by `.` are called node names (`nodeName`).
+- For example, `root.a.b.c` is a path with a depth of 4 levels, where `root`, `a`, `b`, and `c` are all node names.
+
+#### Constraints
+
+- **Reserved keyword `root`**: `root` is a reserved keyword that is only allowed at the beginning of a path. If `root` appears in any other level, the system will fail to parse it and report an error.
+- **Character support**: Except for the first level (`root`), other levels support the following characters:
+  - Letters (`a-z`, `A-Z`)
+  - Digits (`0-9`)
+  - Underscores (`_`)
+  - UNICODE Chinese characters (`\u2E80` to `\u9FFF`)
+- **Case sensitivity**: On Windows systems, path node names in the database are case-insensitive. For example, `root.ln` and `root.LN` are considered the same path.
+
+### Special Characters (Backquote)
+
+If special characters (such as spaces or punctuation marks) are needed in a `nodeName`, you can enclose the node name in Backquote (`). For more information on the use of backticks, please refer to [Backquote](../SQL-Manual/Syntax-Rule.md#reverse-quotation-marks).
+
+### Path Pattern
+
+To make it more convenient and efficient to express multiple time series, IoTDB provides paths with wildcards `*` and `**`. Wildcards can appear in any level of a path.
+
+- **Single-level wildcard (`\*`)**: Represents one level in a path.
+  - For example, `root.vehicle.*.sensor1` represents paths with a depth of 4 levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+- **Multi-level wildcard (`\**`)**: Represents one or more levels (`*`+).
+  - For example:
+    - `root.vehicle.device1.**` represents all paths with a depth of 4 or more levels, prefixed by `root.vehicle.device1`.
+    - `root.vehicle.**.sensor1` represents paths with a depth of 4 or more levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+
+**Note**: `*` and `**` cannot be placed at the beginning of a path.
 
 ### Show Child Paths
 

src/UserGuide/Master/Tree/Basic-Concept/Write-Delete-Data.md

@@ -31,7 +31,7 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 ### Use of INSERT Statements
 
-The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md#insert-data) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Background-knowledge/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Background-knowledge/Data-Type.md)).
+The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md#insert-data) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Basic-Concept/Operate-Metadata.md) and a sensor acquisition value (see [Data Type](../Background-knowledge/Data-Type.md)).
 
 **Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically recognized and registered in the database, achieving automatic modeling.
 
@@ -244,7 +244,7 @@ delete from root.ln.wf02.wt02.status
 
 ### Delete Multiple Timeseries
 
-If both the power supply status and hardware version of the ln group wf02 plant wt02 device before 2017-11-01 16:26:00 need to be deleted, [the prefix path with broader meaning or the path with star](../Background-knowledge/Data-Model-and-Terminology.md) can be used to delete the data. The SQL statement for this operation is:
+If both the power supply status and hardware version of the ln group wf02 plant wt02 device before 2017-11-01 16:26:00 need to be deleted, [the prefix path with broader meaning or the path with star](../Basic-Concept/Operate-Metadata.md) can be used to delete the data. The SQL statement for this operation is:
 
 ```sql
 delete from root.ln.wf02.wt02 where time <= 2017-11-01T16:26:00;

src/UserGuide/Master/Tree/QuickStart/QuickStart_apache.md

@@ -49,7 +49,7 @@ This guide will assist you in quickly installing and deploying IoTDB. You can qu
 
    - Introduction to Time Series Concepts: [Navigating Time Series Data](../Background-knowledge/Navigating_Time_Series_Data.md)
 
-   - Introduction to Modeling Design:[Data Model and Terminology](../Background-knowledge/Data-Model-and-Terminology.md)
+   - Introduction to Modeling Design:[Data Model and Terminology](../Background-knowledge/Data-Model-and-Terminology_apache.md)
 
    - Introduction to SQL syntax[SQL syntax](../Basic-Concept/Operate-Metadata_apache.md)
 

src/UserGuide/Master/Tree/QuickStart/QuickStart_timecho.md

@@ -56,7 +56,7 @@ This guide will assist you in quickly installing and deploying IoTDB. You can qu
 
    - Introduction to Time Series Concepts: [Navigating Time Series Data](../Background-knowledge/Navigating_Time_Series_Data.md)
 
-   - Introduction to Modeling Design:[Data Model and Terminology](../Background-knowledge/Data-Model-and-Terminology.md)
+   - Introduction to Modeling Design:[Data Model and Terminology](../Background-knowledge/Data-Model-and-Terminology_timecho.md)
 
       - Introduction to SQL syntax[SQL syntax](../Basic-Concept/Operate-Metadata_timecho.md)
 

…rGuide/Master/Tree/Reference/Keywords.md …Guide/Master/Tree/SQL-Manual/Keywords.mdsrc/UserGuide/Master/Tree/Reference/Keywords.md renamed to src/UserGuide/Master/Tree/SQL-Manual/Keywords.md src/UserGuide/Master/Tree/Reference/Keywords.md renamed to src/UserGuide/Master/Tree/SQL-Manual/Keywords.md

@@ -1011,7 +1011,59 @@ IoTDB> show timeseries where TAGS(tag1)='v1'
 
 The above operations are supported for timeseries tag, attribute updates, etc.
 
-## Node Management
+## Path query
+
+### Path
+
+A `path` is an expression that conforms to the following constraints:
+
+```sql
+path       
+    : nodeName ('.' nodeName)*
+    ;
+    
+nodeName
+    : wildcard? identifier wildcard?
+    | wildcard
+    ;
+    
+wildcard 
+    : '*' 
+    | '**'
+    ;
+```
+
+###  NodeName
+
+- The parts of a path separated by `.` are called node names (`nodeName`).
+- For example, `root.a.b.c` is a path with a depth of 4 levels, where `root`, `a`, `b`, and `c` are all node names.
+
+#### Constraints
+
+- **Reserved keyword `root`**: `root` is a reserved keyword that is only allowed at the beginning of a path. If `root` appears in any other level, the system will fail to parse it and report an error.
+- **Character support**: Except for the first level (`root`), other levels support the following characters:
+  - Letters (`a-z`, `A-Z`)
+  - Digits (`0-9`)
+  - Underscores (`_`)
+  - UNICODE Chinese characters (`\u2E80` to `\u9FFF`)
+- **Case sensitivity**: On Windows systems, path node names in the database are case-insensitive. For example, `root.ln` and `root.LN` are considered the same path.
+
+### Special Characters (Backquote)
+
+If special characters (such as spaces or punctuation marks) are needed in a `nodeName`, you can enclose the node name in Backquote (`). For more information on the use of backticks, please refer to [Backquote](../SQL-Manual/Syntax-Rule.md#reverse-quotation-marks).
+
+### Path Pattern
+
+To make it more convenient and efficient to express multiple time series, IoTDB provides paths with wildcards `*` and `**`. Wildcards can appear in any level of a path.
+
+- **Single-level wildcard (`\*`)**: Represents one level in a path.
+  - For example, `root.vehicle.*.sensor1` represents paths with a depth of 4 levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+- **Multi-level wildcard (`\**`)**: Represents one or more levels (`*`+).
+  - For example:
+    - `root.vehicle.device1.**` represents all paths with a depth of 4 or more levels, prefixed by `root.vehicle.device1`.
+    - `root.vehicle.**.sensor1` represents paths with a depth of 4 or more levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+
+**Note**: `*` and `**` cannot be placed at the beginning of a path.
 
 ### Show Child Paths
 

…ide/Master/Tree/Reference/Syntax-Rule.md …de/Master/Tree/SQL-Manual/Syntax-Rule.mdsrc/UserGuide/Master/Tree/Reference/Syntax-Rule.md renamed to src/UserGuide/Master/Tree/SQL-Manual/Syntax-Rule.md src/UserGuide/Master/Tree/Reference/Syntax-Rule.md renamed to src/UserGuide/Master/Tree/SQL-Manual/Syntax-Rule.md

@@ -1052,7 +1052,59 @@ IoTDB> show timeseries where TAGS(tag1)='v1'
 
 The above operations are supported for timeseries tag, attribute updates, etc.
 
-## Node Management
+## Path query
+
+### Path
+
+A `path` is an expression that conforms to the following constraints:
+
+```sql
+path       
+    : nodeName ('.' nodeName)*
+    ;
+    
+nodeName
+    : wildcard? identifier wildcard?
+    | wildcard
+    ;
+    
+wildcard 
+    : '*' 
+    | '**'
+    ;
+```
+
+###  NodeName
+
+- The parts of a path separated by `.` are called node names (`nodeName`).
+- For example, `root.a.b.c` is a path with a depth of 4 levels, where `root`, `a`, `b`, and `c` are all node names.
+
+#### Constraints
+
+- **Reserved keyword `root`**: `root` is a reserved keyword that is only allowed at the beginning of a path. If `root` appears in any other level, the system will fail to parse it and report an error.
+- **Character support**: Except for the first level (`root`), other levels support the following characters:
+  - Letters (`a-z`, `A-Z`)
+  - Digits (`0-9`)
+  - Underscores (`_`)
+  - UNICODE Chinese characters (`\u2E80` to `\u9FFF`)
+- **Case sensitivity**: On Windows systems, path node names in the database are case-insensitive. For example, `root.ln` and `root.LN` are considered the same path.
+
+### Special Characters (Backquote)
+
+If special characters (such as spaces or punctuation marks) are needed in a `nodeName`, you can enclose the node name in Backquote (`). For more information on the use of backticks, please refer to [Backquote](../SQL-Manual/Syntax-Rule.md#reverse-quotation-marks).
+
+### Path Pattern
+
+To make it more convenient and efficient to express multiple time series, IoTDB provides paths with wildcards `*` and `**`. Wildcards can appear in any level of a path.
+
+- **Single-level wildcard (`\*`)**: Represents one level in a path.
+  - For example, `root.vehicle.*.sensor1` represents paths with a depth of 4 levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+- **Multi-level wildcard (`\**`)**: Represents one or more levels (`*`+).
+  - For example:
+    - `root.vehicle.device1.**` represents all paths with a depth of 4 or more levels, prefixed by `root.vehicle.device1`.
+    - `root.vehicle.**.sensor1` represents paths with a depth of 4 or more levels, prefixed by `root.vehicle` and suffixed by `sensor1`.
+
+**Note**: `*` and `**` cannot be placed at the beginning of a path.
 
 ### Show Child Paths