diff --git a/src/.vuepress/public/img/data-model-new-1-en.png b/src/.vuepress/public/img/data-model-new-1-en.png new file mode 100644 index 000000000..5c05bd473 Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-1-en.png differ diff --git a/src/.vuepress/public/img/data-model-new-1.png b/src/.vuepress/public/img/data-model-new-1.png new file mode 100644 index 000000000..7a775b249 Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-1.png differ diff --git a/src/.vuepress/public/img/data-model-new-2-en.png b/src/.vuepress/public/img/data-model-new-2-en.png new file mode 100644 index 000000000..32c8ca82d Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-2-en.png differ diff --git a/src/.vuepress/public/img/data-model-new-2.png b/src/.vuepress/public/img/data-model-new-2.png new file mode 100644 index 000000000..90de29748 Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-2.png differ diff --git a/src/.vuepress/public/img/data-model-new-3-en.png b/src/.vuepress/public/img/data-model-new-3-en.png new file mode 100644 index 000000000..9eeb1fbfb Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-3-en.png differ diff --git a/src/.vuepress/public/img/data-model-new-3.png b/src/.vuepress/public/img/data-model-new-3.png new file mode 100644 index 000000000..8d6c9ff09 Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-3.png differ diff --git a/src/.vuepress/public/img/data-model-new-4-en.png b/src/.vuepress/public/img/data-model-new-4-en.png new file mode 100644 index 000000000..0eab87c15 Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-4-en.png differ diff --git a/src/.vuepress/public/img/data-model-new-4.png b/src/.vuepress/public/img/data-model-new-4.png new file mode 100644 index 000000000..2aeda68f4 Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-4.png differ diff --git a/src/.vuepress/public/img/data-model-new-5-en.png b/src/.vuepress/public/img/data-model-new-5-en.png new file mode 100644 index 000000000..fa9dc5c9a Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-5-en.png differ diff --git a/src/.vuepress/public/img/data-model-new-5.png b/src/.vuepress/public/img/data-model-new-5.png new file mode 100644 index 000000000..cd3e57c6e Binary files /dev/null and b/src/.vuepress/public/img/data-model-new-5.png differ diff --git a/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md index a0089b0e7..c6d7e9739 100644 --- a/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -113,7 +113,7 @@ The application scenarios mainly include two categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -165,7 +165,7 @@ The application scenarios mainly include two categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -181,5 +181,5 @@ The application scenarios mainly include two categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
diff --git a/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md index 46a5e3e0d..df755ac48 100644 --- a/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -115,7 +115,7 @@ The application scenarios mainly include three categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -167,7 +167,7 @@ The application scenarios mainly include three categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -183,7 +183,7 @@ The application scenarios mainly include three categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
### 3.3 Scenario 3: Dual-Model Integration @@ -207,7 +207,7 @@ The application scenarios mainly include three categories: - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
- +
##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns? @@ -225,5 +225,5 @@ The application scenarios mainly include three categories: - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
- +
diff --git a/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md index 93a1e5165..6d16ae929 100644 --- a/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -115,7 +115,7 @@ The application scenarios mainly include two categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -167,7 +167,7 @@ The application scenarios mainly include two categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -183,5 +183,5 @@ The application scenarios mainly include two categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
diff --git a/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md index db72885b3..cd3b9e481 100644 --- a/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -117,7 +117,7 @@ The application scenarios mainly include three categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -169,7 +169,7 @@ The application scenarios mainly include three categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -185,7 +185,7 @@ The application scenarios mainly include three categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
### 3.3 Scenario 3: Dual-Model Integration @@ -209,7 +209,7 @@ The application scenarios mainly include three categories: - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
- +
##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns? @@ -227,5 +227,5 @@ The application scenarios mainly include three categories: - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
- +
diff --git a/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md index a0089b0e7..c6d7e9739 100644 --- a/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -113,7 +113,7 @@ The application scenarios mainly include two categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -165,7 +165,7 @@ The application scenarios mainly include two categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -181,5 +181,5 @@ The application scenarios mainly include two categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
diff --git a/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md index 46a5e3e0d..df755ac48 100644 --- a/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -115,7 +115,7 @@ The application scenarios mainly include three categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -167,7 +167,7 @@ The application scenarios mainly include three categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -183,7 +183,7 @@ The application scenarios mainly include three categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
### 3.3 Scenario 3: Dual-Model Integration @@ -207,7 +207,7 @@ The application scenarios mainly include three categories: - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
- +
##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns? @@ -225,5 +225,5 @@ The application scenarios mainly include three categories: - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
- +
diff --git a/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md index 93a1e5165..6d16ae929 100644 --- a/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -115,7 +115,7 @@ The application scenarios mainly include two categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -167,7 +167,7 @@ The application scenarios mainly include two categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -183,5 +183,5 @@ The application scenarios mainly include two categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
diff --git a/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md index db72885b3..cd3b9e481 100644 --- a/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -117,7 +117,7 @@ The application scenarios mainly include three categories: - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
- +
##### 3.1.3.2 How to model when there are no devices, only data points? @@ -169,7 +169,7 @@ The application scenarios mainly include three categories: - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
- +
##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns? @@ -185,7 +185,7 @@ The application scenarios mainly include three categories: - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
- +
### 3.3 Scenario 3: Dual-Model Integration @@ -209,7 +209,7 @@ The application scenarios mainly include three categories: - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
- +
##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns? @@ -227,5 +227,5 @@ The application scenarios mainly include three categories: - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
- +
diff --git a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md index 2df0738e6..a5c12864d 100644 --- a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -114,7 +114,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -166,7 +166,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -182,5 +182,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
diff --git a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md index a9f8d568a..fc796b78d 100644 --- a/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -115,7 +115,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -167,7 +167,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -183,7 +183,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -207,7 +207,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -227,5 +227,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：按照设备分类，建立多个表对每一层结构信息进行管理。
- +
diff --git a/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md index c6eaaee83..cf3c76bf8 100644 --- a/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -116,7 +116,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -168,7 +168,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -184,5 +184,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
diff --git a/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md index 320f4dc63..0686f14d1 100644 --- a/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/zh/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -118,7 +118,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -170,7 +170,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -186,7 +186,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -210,7 +210,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -230,5 +230,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：按照设备分类，建立多个表对每一层结构信息进行管理。
- +
diff --git a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md index 2df0738e6..7c6f00aef 100644 --- a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -114,7 +114,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -166,7 +166,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -182,5 +182,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
diff --git a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md index a9f8d568a..619267dc2 100644 --- a/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/zh/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -115,7 +115,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -167,7 +167,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -183,7 +183,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -207,7 +207,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -227,5 +227,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：按照设备分类，建立多个表对每一层结构信息进行管理。
- +
diff --git a/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md b/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md index c6eaaee83..cf3c76bf8 100644 --- a/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md +++ b/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md @@ -116,7 +116,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -168,7 +168,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -184,5 +184,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
diff --git a/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md b/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md index 320f4dc63..0686f14d1 100644 --- a/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md +++ b/src/zh/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md @@ -118,7 +118,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -170,7 +170,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -186,7 +186,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -210,7 +210,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -230,5 +230,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点 - 表视图：按照设备分类，建立多个表对每一层结构信息进行管理。
- +