Test/sangshuduo/td 13408 move example back (#10466)

* [TD-13408]<test>: move examples back

* [TD-13408]<test>: move examples back

* add examples/c to CMakeLists.txt

* update tests

* [TD-13408]<test>: move rust example back

* fix examples path for Windows

* fix tests/exmaples

cmake/install.inc

@@ -9,7 +9,7 @@ ELSEIF (TD_WINDOWS)
   INSTALL(DIRECTORY ${TD_COMMUNITY_DIR}/src/connector/nodejs DESTINATION connector)
   INSTALL(DIRECTORY ${TD_COMMUNITY_DIR}/src/connector/python DESTINATION connector)
   INSTALL(DIRECTORY ${TD_COMMUNITY_DIR}/src/connector/C\# DESTINATION connector)
-  INSTALL(DIRECTORY ${TD_COMMUNITY_DIR}/tests/examples DESTINATION .)
+  INSTALL(DIRECTORY ${TD_COMMUNITY_DIR}/examples DESTINATION .)
   INSTALL(FILES ${TD_COMMUNITY_DIR}/packaging/cfg/taos.cfg DESTINATION cfg)
   INSTALL(FILES ${TD_COMMUNITY_DIR}/src/inc/taos.h DESTINATION include)
   INSTALL(FILES ${TD_COMMUNITY_DIR}/src/inc/taoserror.h DESTINATION include)

documentation20/en/07.advanced-features/docs.md

@@ -83,7 +83,7 @@ taos_consume
 taos_unsubscribe
 ```
 
-Please refer to the [C/C++ Connector](https://www.taosdata.com/cn/documentation/connector/) for the documentation of these APIs. The following is still a smart meter scenario as an example to introduce their specific usage (please refer to the previous section "Continuous Query" for the structure of STables and sub-tables). The complete sample code can be found [here](https://github.com/taosdata/TDengine/blob/master/tests/examples/c/subscribe.c).
+Please refer to the [C/C++ Connector](https://www.taosdata.com/cn/documentation/connector/) for the documentation of these APIs. The following is still a smart meter scenario as an example to introduce their specific usage (please refer to the previous section "Continuous Query" for the structure of STables and sub-tables). The complete sample code can be found [here](https://github.com/taosdata/TDengine/blob/master/examples/c/subscribe.c).
 
 If we want to be notified and do some process when the current of a smart meter exceeds a certain limit (e.g. 10A), there are two methods: one is to query each sub-table separately, record the timestamp of the last piece of data after each query, and then only query all data after this timestamp:
 
@@ -210,8 +210,8 @@ After introducing the code, let's take a look at the actual running effect. For
 You can compile and start the sample program by executing the following command in the directory where the sample code is located:
 
 ```shell
-$ make
-$ ./subscribe -sql='select * from meters where current > 10;'
+make
+./subscribe -sql='select * from meters where current > 10;'
 ```
 
 After the sample program starts, open another terminal window, and the shell that starts TDengine inserts a data with a current of 12A into **D1001**:

documentation20/en/08.connector/docs.md

@@ -30,9 +30,9 @@ Note:
 
 The server should already have the TDengine server package installed. The connector driver installation steps are as follows:
 
-**Linux**
+### Linux
 
-**1. Download from TAOS Data website(https://www.taosdata.com/cn/all-downloads/)**
+**1. Download from TAOS Data [official website](https://www.taosdata.com/cn/all-downloads/)**
 
 * X64 hardware environment: TDengine-client-2.x.x.x-Linux-x64.tar.gz
 * ARM64 hardware environment: TDengine-client-2.x.x.x-Linux-aarch64.tar.gz
@@ -74,7 +74,7 @@ Edit the taos.cfg file (default path/etc/taos/taos.cfg) and change firstEP to En
 
 **Windows x64/x86**
 
-**1. Download from TAOS Data website(https://www.taosdata.com/cn/all-downloads/)**
+**1. Download from TAOS Data [official website](https://www.taosdata.com/cn/all-downloads/)**
 
 * X64 hardware environment: TDengine-client-2.X.X.X-Windows-x64.exe
 * X86 hardware environment: TDengine-client-2.X.X.X-Windows-x86.exe
@@ -167,7 +167,7 @@ Note:
 - The TDengine dynamic library needs to be linked at compiling. The library in Linux is *libtaos.so*, which installed at/usr/local/taos/driver. By Windows, it is taos.dll and installed at C:\ TDengine.
 - Unless otherwise specified, when the return value of API is an integer, 0 represents success, others are error codes representing the cause of failure, and when the return value is a pointer, NULL represents failure.
 
-More sample codes for using C/C++ connectors, please visit https://github.com/taosdata/TDengine/tree/develop/examples/c.
+More sample codes for using C/C++ connectors, please visit `https://github.com/taosdata/TDengine/tree/develop/examples/c`.
 
 ### Basic API
 
@@ -204,7 +204,6 @@ Create a database connection and initialize the connection context. The paramete
 A null return value indicates a failure. The application needs to save the returned parameters for subsequent API calls.
 Note: The same process can connect to multiple taosd processes based on ip/port
 
-
 - `char *taos_get_server_info(TAOS *taos)`
 
 Get version information of the server-side.
@@ -305,7 +304,6 @@ Asynchronous APIs have relatively high requirements for users, who can selective
 
 The asynchronous APIs of TDengine all use non-blocking calling mode. Applications can use multithreading to open multiple tables at the same time, and can query or insert to each open table at the same time. It should be pointed out that the **application client must ensure that the operation on the same table is completely serialized**, that is, when the insertion or query operation on the same table is not completed (when no result returned), the second insertion or query operation cannot be performed.
 
-
 <a class="anchor" id="stmt"></a>
 ### Parameter binding API
 
@@ -626,12 +624,12 @@ Refer to [JSON type instructions](https://www.taosdata.com/en/documentation/taos
 
 So far Python still does not completely support nanosecond type. Please refer to the link 1 and 2. The implementation of the python connector is to return an integer number for nanosecond value rather than datatime type as what ms and us do. The developer needs to handle it themselves. We recommend using pandas to_datetime() function. If Python officially support nanosecond in the future, TAOS Data might be possible to change the interface accordingly, which mean the application need change too.
 
-1. https://stackoverflow.com/questions/10611328/parsing-datetime-strings-containing-nanoseconds
-2. https://www.python.org/dev/peps/pep-0564/
+1. `https://stackoverflow.com/questions/10611328/parsing-datetime-strings-containing-nanoseconds`
+2. `https://www.python.org/dev/peps/pep-0564/`
 
 #### Helper
 
-Users can directly view the usage information of the module through Python's helper, or refer to the sample program in tests/examples/Python. The following are some common classes and methods:
+Users can directly view the usage information of the module through Python's helper, or refer to the sample program in the `examples/Python` directory. The following are some common classes and methods:
 
 - *TDengineConnection* class
 
@@ -647,7 +645,7 @@ Used to generate an instance of taos.TDengineConnection.
 
 ### Python connector code sample
 
-In tests/examples/python, we provide a sample Python program read_example. py to guide you to design your own write and query program. After installing the corresponding client, introduce the taos class through `import taos`. The steps are as follows:
+In the `examples/python` directory, we provide a sample Python program read_example. py to guide you to design your own write and query program. After installing the corresponding client, introduce the taos class through `import taos`. The steps are as follows:
 
 - Get the `TDengineConnection` object through `taos.connect`, which can be applied for only one by a program and shared among multiple threads.
 
@@ -678,7 +676,7 @@ Parameter description:
 - IP: Any host in the cluster
 - PORT: httpPort configuration item in the configuration file, defaulting to 6041
 
-For example: http://192.168.0.1:6041/rest/sql is a URL that points to an IP address of 192.168.0.1.
+For example: `http://192.168.0.1:6041/rest/sql` is a URL that points to an IP address of 192.168.0.1.
 
 The header of HTTP request needs to carry identity authentication information. TDengine supports Basic authentication and custom authentication. Subsequent versions will provide standard and secure digital signature mechanism for identity authentication.
 
@@ -877,32 +875,33 @@ Only some configuration parameters related to RESTful interface are listed below
 - httpEnableCompress: Compression is not supported by default. Currently, TDengine only supports gzip compression format
 - httpdebugflag: Logging switch, 131: error and alarm information only, 135: debugging information, 143: very detailed debugging information, default 131
 
-
-
 ## <a class="anchor" id="csharp"></a> CSharp Connector
 
-
 * The C # connector supports: Linux 64/Windows x64/Windows x86.
 * C# connector can be download and include as normal table form [Nuget.org](https://www.nuget.org/packages/TDengine.Connector/).
 * On Windows, C # applications can use the native C interface of TDengine to perform all database operations, and future versions will provide the ORM (Dapper) framework driver.
 
 ### Installation preparation
 
-* For application driver installation, please refer to the[ steps of installing connector driver](https://www.taosdata.com/en/documentation/connector#driver).
+* For application driver installation, please refer to the [steps of installing connector driver](https://www.taosdata.com/en/documentation/connector#driver).
 * .NET interface file TDengineDrivercs.cs and reference sample TDengineTest.cs are both located in the Windows client install_directory/examples/C# directory.
 * Install [.NET SDK](https://dotnet.microsoft.com/download)
 
 ### Example Source Code
+
 you can find sample code under follow directions:
+
 * {client_install_directory}/examples/C#
 * [github C# example source code](https://github.com/taosdata/TDengine/tree/develop/examples/C%2523)
 
 **Tips:** TDengineTest.cs       One of C# connector's sample code that include basic examples like connection,sql executions and so on.
 
 ### Installation verification
+
 Run {client_install_directory}/examples/C#/C#Checker/C#Checker.cs
 
 Need install .Net SDK first
+
 ```cmd
 cd {client_install_directory}/examples/C#/C#Checker
 //run c#checker.cs
@@ -910,24 +909,31 @@ dotnet run -- -h <FQDN> //dotnet run will build project first by default.
 ```
 
 ### How to use C# connector
+
 On Windows system, .NET applications can use the .NET interface of TDengine to perform all database operations. The steps to use it are as follows:
 
 need to install .NET SDK first
+
 * create a c# project.
+
 ``` cmd
 mkdir test
 cd test
 dotnet new console
 ```
+
 * add TDengineDriver as an package through Nuget
 
 ``` cmd
 dotnet add package TDengine.Connector
 ```
+
 * include the TDnengineDriver in you application's namespace
+
 ```C#
 using TDengineDriver;
 ```
+
 * user can reference from[TDengineTest.cs](https://github.com/taosdata/TDengine/tree/develop/examples/C%2523/TDengineTest) and learn how to define database connection,query,insert and other basic data manipulations.
 
 **Note:**
@@ -953,9 +959,9 @@ https://www.taosdata.com/blog/2020/11/02/1901.html
 
 - For application driver installation, please refer to the [steps of installing connector driver](https://www.taosdata.com/en/documentation/connector#driver).
 
-The TDengine provides the GO driver taosSql. taosSql implements the GO language's built-in interface database/sql/driver. Users can access TDengine in the application by simply importing the package as follows, see https://github.com/taosdata/driver-go/blob/develop/taosSql/driver_test.go for details.
+The TDengine provides the GO driver taosSql. taosSql implements the GO language's built-in interface database/sql/driver. Users can access TDengine in the application by simply importing the package as follows, see `https://github.com/taosdata/driver-go/blob/develop/taosSql/driver_test.go` for details.
 
-Sample code for using the Go connector can be found in https://github.com/taosdata/TDengine/tree/develop/examples/go .
+Sample code for using the Go connector can be found in `https://github.com/taosdata/TDengine/tree/develop/examples/go`.
 
 ```Go
 import (
@@ -1071,7 +1077,7 @@ After installing the TDengine client, the nodejsChecker.js program can verify wh
 
 Steps:
 
-1. Create a new installation verification directory, for example: `~/tdengine-test`, copy the nodejsChecker.js source program on github. Download address: （https://github.com/taosdata/TDengine/tree/develop/examples/nodejs/nodejsChecker.js）.
+1. Create a new installation verification directory, for example: `~/tdengine-test`, copy the nodejsChecker.js source program on github. Download address: `https://github.com/taosdata/TDengine/tree/develop/examples/nodejs/nodejsChecker.js`.
 
 2. Execute the following command: