diff --git a/src/.vuepress/public/img/data-modeling-new-1-en.png b/src/.vuepress/public/img/data-modeling-new-1-en.png new file mode 100644 index 000000000..76fc329d6 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-1-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-1.png b/src/.vuepress/public/img/data-modeling-new-1.png new file mode 100644 index 000000000..146a417a9 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-1.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-10-en.png b/src/.vuepress/public/img/data-modeling-new-10-en.png new file mode 100644 index 000000000..6660b7947 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-10-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-10.png b/src/.vuepress/public/img/data-modeling-new-10.png new file mode 100644 index 000000000..a08206e59 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-10.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-2-en.png b/src/.vuepress/public/img/data-modeling-new-2-en.png new file mode 100644 index 000000000..e5272403d Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-2-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-2.png b/src/.vuepress/public/img/data-modeling-new-2.png new file mode 100644 index 000000000..b32ccb947 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-2.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-3.png b/src/.vuepress/public/img/data-modeling-new-3.png new file mode 100644 index 000000000..f6f35fad1 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-3.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-4-en.png b/src/.vuepress/public/img/data-modeling-new-4-en.png new file mode 100644 index 000000000..c740dc695 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-4-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-4.png b/src/.vuepress/public/img/data-modeling-new-4.png new file mode 100644 index 000000000..7c227d724 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-4.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-5-en.png b/src/.vuepress/public/img/data-modeling-new-5-en.png new file mode 100644 index 000000000..1d77f1812 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-5-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-5.png b/src/.vuepress/public/img/data-modeling-new-5.png new file mode 100644 index 000000000..04911476c Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-5.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-6-en.png b/src/.vuepress/public/img/data-modeling-new-6-en.png new file mode 100644 index 000000000..43ae31937 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-6-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-6.png b/src/.vuepress/public/img/data-modeling-new-6.png new file mode 100644 index 000000000..784d01023 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-6.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-7-en.png b/src/.vuepress/public/img/data-modeling-new-7-en.png new file mode 100644 index 000000000..eac2a224f Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-7-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-7.png b/src/.vuepress/public/img/data-modeling-new-7.png new file mode 100644 index 000000000..d6f9d0115 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-7.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-8-en.png b/src/.vuepress/public/img/data-modeling-new-8-en.png new file mode 100644 index 000000000..e7da7f849 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-8-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-8.png b/src/.vuepress/public/img/data-modeling-new-8.png new file mode 100644 index 000000000..0b6224432 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-8.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-9-en.png b/src/.vuepress/public/img/data-modeling-new-9-en.png new file mode 100644 index 000000000..9156936d5 Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-9-en.png differ diff --git a/src/.vuepress/public/img/data-modeling-new-9.png b/src/.vuepress/public/img/data-modeling-new-9.png new file mode 100644 index 000000000..0f289e8cf Binary files /dev/null and b/src/.vuepress/public/img/data-modeling-new-9.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 0d2124dc2..ddf1626c0 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 @@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -273,7 +273,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 mode when there are no devices, only data points? @@ -281,7 +281,7 @@ The application scenarios mainly include two categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -289,7 +289,7 @@ The application scenarios mainly include two categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -325,7 +325,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 mode when there are no device identifier columns or attribute columns? @@ -333,7 +333,7 @@ The application scenarios mainly include two categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -341,5 +341,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 88537b320..82f89222d 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 @@ -234,7 +234,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../User-Manual/Tree-to-Table_timecho.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -274,7 +274,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 mode when there are no devices, only data points? @@ -282,7 +282,7 @@ The application scenarios mainly include three categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -290,7 +290,7 @@ The application scenarios mainly include three categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -326,7 +326,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 mode when there are no device identifier columns or attribute columns? @@ -334,7 +334,7 @@ The application scenarios mainly include three categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -342,7 +342,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-Mode Integration @@ -366,7 +366,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 mode when there are no device identifier columns or attribute columns? @@ -375,7 +375,7 @@ The application scenarios mainly include three categories: - **Table View**: Place all data points into a single table. There is no limit to the number of data point columns; it can reach hundreds of thousands. If data points have the same data type, they can be treated as the same type of device.
- +
##### 3.3.2.3 How to mode when a device has both sub-devices and data points? @@ -384,5 +384,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 ef9510cfe..b98bd5989 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 @@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../../latest-Table/User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -278,7 +278,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 when there are no devices, only data points? @@ -286,7 +286,7 @@ The application scenarios mainly include two categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -294,7 +294,7 @@ The application scenarios mainly include two categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -330,7 +330,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 mode when there are no device identifier columns or attribute columns? @@ -338,7 +338,7 @@ The application scenarios mainly include two categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -346,5 +346,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 6b6e2018d..0f3b1ac5e 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 @@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../../latest-Table/User-Manual/Tree-to-Table_timecho.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -279,7 +279,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 mode when there are no devices, only data points? @@ -287,7 +287,7 @@ The application scenarios mainly include three categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -295,7 +295,7 @@ The application scenarios mainly include three categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -331,7 +331,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 mode when there are no device identifier columns or attribute columns? @@ -339,7 +339,7 @@ The application scenarios mainly include three categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -347,7 +347,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-Mode Integration @@ -371,7 +371,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 mode when there are no device identifier columns or attribute columns? @@ -380,7 +380,7 @@ The application scenarios mainly include three categories: - **Table View**: Place all data points into a single table. There is no limit to the number of data point columns; it can reach hundreds of thousands. If data points have the same data type, they can be treated as the same type of device.
- +
##### 3.3.2.3 How to mode when a device has both sub-devices and data points? @@ -389,5 +389,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 0d2124dc2..ddf1626c0 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 @@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -273,7 +273,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 mode when there are no devices, only data points? @@ -281,7 +281,7 @@ The application scenarios mainly include two categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -289,7 +289,7 @@ The application scenarios mainly include two categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -325,7 +325,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 mode when there are no device identifier columns or attribute columns? @@ -333,7 +333,7 @@ The application scenarios mainly include two categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -341,5 +341,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 88537b320..82f89222d 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 @@ -234,7 +234,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../User-Manual/Tree-to-Table_timecho.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -274,7 +274,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 mode when there are no devices, only data points? @@ -282,7 +282,7 @@ The application scenarios mainly include three categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -290,7 +290,7 @@ The application scenarios mainly include three categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -326,7 +326,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 mode when there are no device identifier columns or attribute columns? @@ -334,7 +334,7 @@ The application scenarios mainly include three categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -342,7 +342,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-Mode Integration @@ -366,7 +366,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 mode when there are no device identifier columns or attribute columns? @@ -375,7 +375,7 @@ The application scenarios mainly include three categories: - **Table View**: Place all data points into a single table. There is no limit to the number of data point columns; it can reach hundreds of thousands. If data points have the same data type, they can be treated as the same type of device.
- +
##### 3.3.2.3 How to mode when a device has both sub-devices and data points? @@ -384,5 +384,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 ef9510cfe..b98bd5989 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 @@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../../latest-Table/User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -278,7 +278,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 when there are no devices, only data points? @@ -286,7 +286,7 @@ The application scenarios mainly include two categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -294,7 +294,7 @@ The application scenarios mainly include two categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -330,7 +330,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 mode when there are no device identifier columns or attribute columns? @@ -338,7 +338,7 @@ The application scenarios mainly include two categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -346,5 +346,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 6b6e2018d..0f3b1ac5e 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 @@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection( IoTDB supports **tree-to-table conversion**, as shown in the figure below: -![](/img/tree-to-table-en-1.png) +![](/img/data-modeling-new-1-en.png) This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../../latest-Table/User-Manual/Tree-to-Table_timecho.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**. @@ -279,7 +279,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 mode when there are no devices, only data points? @@ -287,7 +287,7 @@ The application scenarios mainly include three categories: - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
- +
##### 3.1.3.3 How to mode when a device has both sub-devices and data points? @@ -295,7 +295,7 @@ The application scenarios mainly include three categories: - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
- +
@@ -331,7 +331,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 mode when there are no device identifier columns or attribute columns? @@ -339,7 +339,7 @@ The application scenarios mainly include three categories: - There is no limit to the number of columns; it can reach hundreds of thousands.
- +
##### 3.2.3.3 How to mode when a device has both sub-devices and data points? @@ -347,7 +347,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-Mode Integration @@ -371,7 +371,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 mode when there are no device identifier columns or attribute columns? @@ -380,7 +380,7 @@ The application scenarios mainly include three categories: - **Table View**: Place all data points into a single table. There is no limit to the number of data point columns; it can reach hundreds of thousands. If data points have the same data type, they can be treated as the same type of device.
- +
##### 3.3.2.3 How to mode when a device has both sub-devices and data points? @@ -389,5 +389,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 c951dcf63..594884a24 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 @@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../User-Manual/Tree-to-Table_apache.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -274,7 +274,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -282,7 +282,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -290,7 +290,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -326,7 +326,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -334,7 +334,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -342,5 +342,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 4bd0c054a..8f41796cf 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 @@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../User-Manual/Tree-to-Table_timecho.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -275,7 +275,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -283,7 +283,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -291,7 +291,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -327,7 +327,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -335,7 +335,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -343,7 +343,7 @@ IoTDB 提供了树转表功能，如下图所示： - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -367,7 +367,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -377,7 +377,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：将所有测点放入一张表中，测点列数没有数量限制，可以达到数十万以上。若测点具有相同的数据类型，可将测点作为同一类设备。
- +
##### 3.3.2.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -387,5 +387,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 fb63d7fe8..911a612f9 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 @@ -238,7 +238,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../../latest-Table/User-Manual/Tree-to-Table_apache.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -278,7 +278,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -286,7 +286,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -294,7 +294,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -330,7 +330,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -338,7 +338,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -346,5 +346,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 c56987874..c2787485d 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 @@ -238,7 +238,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../../latest-Table/User-Manual/Tree-to-Table_timecho.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -279,7 +279,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -287,7 +287,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -295,7 +295,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -331,7 +331,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -339,7 +339,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -347,7 +347,7 @@ IoTDB 提供了树转表功能，如下图所示： - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -371,7 +371,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -381,7 +381,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：将所有测点放入一张表中，测点列数没有数量限制，可以达到数十万以上。若测点具有相同的数据类型，可将测点作为同一类设备。
- +
##### 3.3.2.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -391,5 +391,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 c951dcf63..594884a24 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 @@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../User-Manual/Tree-to-Table_apache.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -274,7 +274,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -282,7 +282,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -290,7 +290,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -326,7 +326,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -334,7 +334,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -342,5 +342,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 4bd0c054a..8f41796cf 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 @@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../User-Manual/Tree-to-Table_timecho.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -275,7 +275,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -283,7 +283,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -291,7 +291,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -327,7 +327,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -335,7 +335,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -343,7 +343,7 @@ IoTDB 提供了树转表功能，如下图所示： - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -367,7 +367,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -377,7 +377,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：将所有测点放入一张表中，测点列数没有数量限制，可以达到数十万以上。若测点具有相同的数据类型，可将测点作为同一类设备。
- +
##### 3.3.2.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -387,5 +387,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 fb63d7fe8..911a612f9 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 @@ -238,7 +238,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../../latest-Table/User-Manual/Tree-to-Table_apache.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -278,7 +278,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -286,7 +286,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -294,7 +294,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -330,7 +330,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -338,7 +338,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -346,5 +346,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 c56987874..c2787485d 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 @@ -238,7 +238,7 @@ Connection connection = DriverManager.getConnection( IoTDB 提供了树转表功能，如下图所示： -![](/img/tree-to-table-1.png) +![](/img/data-modeling-new-1.png) 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../../latest-Table/User-Manual/Tree-to-Table_timecho.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。 @@ -279,7 +279,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
- +
##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？ @@ -287,7 +287,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
- +
##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -295,7 +295,7 @@ IoTDB 提供了树转表功能，如下图所示： - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
- +
@@ -331,7 +331,7 @@ IoTDB 提供了树转表功能，如下图所示： - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
- +
##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？ @@ -339,7 +339,7 @@ IoTDB 提供了树转表功能，如下图所示： - 列数没有数量限制，可以达到数十万以上。
- +
##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -347,7 +347,7 @@ IoTDB 提供了树转表功能，如下图所示： - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
- +
### 3.3 场景三：双模型结合 @@ -371,7 +371,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
- +
##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？ @@ -381,7 +381,7 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：将所有测点放入一张表中，测点列数没有数量限制，可以达到数十万以上。若测点具有相同的数据类型，可将测点作为同一类设备。
- +
##### 3.3.2.3 如果在一个设备下，既有子设备，也有测点，如何建模？ @@ -391,5 +391,5 @@ IoTDB 提供了树转表功能，如下图所示： - 表视图：按照设备分类，建立多个表对每一层结构信息进行管理。
- +