Both the modeling and writing chapters have added explanations for no… (#491)

Author: W1y1r

src/UserGuide/Master/Tree/Basic-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**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.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

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

@@ -33,6 +33,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 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/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Basic-Concept/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.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V0.13.x/Data-Concept/Data-Model-and-Terminology.md

@@ -53,6 +53,8 @@ After a storage group is set, the ancestral layers, children and descendant laye
 
 The Layer Name of storage group can only consist of characters, numbers and underscores, like `root.storagegroup_1`.
 
+**Schema-less writing**: When metadata is not defined, data can be directly written through an insert statement, and the required metadata will be automatically identified and registered in the storage group, achieving automatic modeling.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V0.13.x/Write-And-Delete-Data/Write-Data.md

@@ -29,6 +29,8 @@ This section mainly introduces the use of [INSERT SQL statement](../Reference/SQ
 
 The [INSERT SQL statement](../Reference/SQL-Reference.md) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Data-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Data-Concept/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 identified and registered in the storage group, achieving automatic modeling.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V1.0.x/Data-Concept/Data-Model-and-Terminology.md

@@ -55,6 +55,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**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.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V1.0.x/Write-Data/Write-Data.md

@@ -31,6 +31,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../Reference/SQL-Reference.md) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Data-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Data-Concept/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.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V1.1.x/Data-Concept/Data-Model-and-Terminology.md

@@ -55,6 +55,8 @@ After a database is set, the ancestral layers, children and descendant layers of
 
 The Layer Name of database can only consist of characters, numbers, and underscores, like `root.storagegroup_1`.
 
+**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.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V1.1.x/Write-Data/Write-Data.md

@@ -31,6 +31,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../Reference/SQL-Reference.md) statement is used to insert data into one or more specified timeseries created. For each point of data inserted, it consists of a [timestamp](../Data-Concept/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Data-Concept/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.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows:

src/UserGuide/V1.2.x/Basic-Concept/Data-Model-and-Terminology.md

@@ -57,6 +57,8 @@ The Layer Name of database can only consist of characters, numbers, and undersco
 
 > Note ：Database name do not support enclosing * in back quotes, e.g., root.\ ` * \ `, but the rest of the level is free of this restriction.
 
+**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.
+
 ### Path
 
 A `path` is an expression that conforms to the following constraints:

src/UserGuide/V1.2.x/User-Manual/Write-Delete-Data.md

@@ -33,6 +33,8 @@ Writing a repeat timestamp covers the original timestamp data, which can be rega
 
 The [INSERT SQL statement](../SQL-Manual/SQL-Manual.md) 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/Data-Model-and-Terminology.md) and a sensor acquisition value (see [Data Type](../Basic-Concept/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.
+
 In the scenario of this section, take two timeseries `root.ln.wf02.wt02.status` and `root.ln.wf02.wt02.hardware` as an example, and their data types are BOOLEAN and TEXT, respectively.
 
 The sample code for single column data insertion is as follows: