TAOS SQL

TDengine provides a SQL-style language, TAOS SQL, to insert or query data. This document introduces TAOS SQL and supports other common tips. To read through this document, readers should have basic understanding about SQL.

TAOS SQL is the main tool for users to write and query data into/from TDengine. TAOS SQL provides a syntax style similar to standard SQL to facilitate users to get started quickly. Strictly speaking, TAOS SQL is not and does not attempt to provide SQL standard syntax. In addition, since TDengine does not provide deletion functionality for time-series data, the relevant functions of data deletion is unsupported in TAO SQL.

Let’s take a look at the conventions used for syntax descriptions.

The content in < > is what the user needs to enter, but do not enter < > itself
[] indicates that the content is optional, but do not enter [] itself
"|" means you can select one of multiple choices, but you cannot enter | yourself
"…" means repeating for as many times

In order to better explain the rules and characteristics of SQL syntax, this document assumes that there is a data set. Take smart meters as an example, each smart meter collects three metrics: current, voltage and phase. It is modeled as follows:

taos> DESCRIBE meters;
             Field              |        Type        |   Length    |    Note    |
=================================================================================
 ts                             | TIMESTAMP          |           8 |            |
 current                        | FLOAT              |           4 |            |
 voltage                        | INT                |           4 |            |
 phase                          | FLOAT              |           4 |            |
 location                       | BINARY             |          64 | TAG        |
 groupid                        | INT                |           4 | TAG        |

The data set contains data from four smart meters, which correspond to four sub-tables according to the modeling rules of TDengine, and their names are D1001, D1002, D1003 and D1004 respectively.

Data Types

With TDengine, the most important thing is timestamp. When creating and inserting records and querying history records, you need to specify a timestamp. The timestamp has the following rules:

Time Format: 'YYYY-MM-DD HH:mm:ss.MS', default in milliseconds. For example,'2017-08-12 18:52:58.128'
Internal Function now : this is the current time of the server
When inserting a record, if timestamp is NOW, then use the server current time.
Epoch Time: a timestamp value can also be a long integer representing milliseconds since 1970-01-01 08:00:00.000.
Arithmetic operations can be applied to timestamp. For example: now-2h represents a timestamp which is 2 hours ago from the current server time. Units include u( microsecond), a (milliseconds), s (seconds), m (minutes), h (hours), d (days), w (weeks). In select * from t1 where ts > now-2w and ts <= now-1w, which queries data of the whole week before two weeks. To specify the interval of down sampling, you can also use n(calendar month) and y(calendar year) as time units.

TDengine's timestamp is set to millisecond accuracy by default. Microsecond/nanosecond accuracy can be set using CREATE DATABASE with PRECISION parameter. (Nanosecond resolution is supported from version 2.1.5.0 onwards.)

In TDengine, the following 10 data types can be used in data model of an ordinary table.

	Data Type	Bytes	Note
1	TIMESTAMP	8	Time stamp. Default in milliseconds, and support microseconds. Starting from 1970-01-01 00:00:00. 000 (UTC/GMT), the timing cannot be earlier than this time.
2	INT	4	A null-able integer type with a range of [-2^31+1, 2^31-1 ]
3	BIGINT	8	A null-able integer type with a range of [-2^59, 2^59 ]
4	FLOAT	4	A standard null-able float type with 6 -7 significant digits and a range of [-3.4E38, 3.4E38]
5	DOUBLE	8	A standard null-able double float type with 15-16 significant digits and a range of [-1.7E308, 1.7E308]
6	BINARY	Custom	Used to record ASCII strings. Theoretically, the maximum length can be 16,374 bytes, but since each row of data can be up to 16K bytes, the actual limit is generally smaller than the theoretical value. Binary only supports string input, and single quotation marks are used at both ends of the string, otherwise all English will be automatically converted to lowercase. When using, the size must be specified. For example, binary (20) defines a string with a maximum length of 20 characters, and each character occupies 1 byte of storage space. In this case, if the user string exceeds 20 bytes, an error will be reported. For single quotation marks in strings, they can be represented by escape character backslash plus single quotation marks, that is\ '.
7	SMALLINT	2	A null-able integer type with a range of [-32767, 32767]
8	TINYINT	1	A null-able integer type with a range of [-127, 127]
9	BOOL	1	Boolean type，{true, false}
10	NCHAR	Custom	Used to record non-ASCII strings, such as Chinese characters. Each nchar character takes up 4 bytes of storage space. Single quotation marks are used at both ends of the string, and escape characters are required for single quotation marks in the string, that is \’. When nchar is used, the string size must be specified. A column of type nchar (10) indicates that the string of this column stores up to 10 nchar characters, which will take up 40 bytes of space. If the length of the user string exceeds the declared length, an error will be reported.
11	JSON		Json type，only support for tag

Tips:

TDengine is case-insensitive to English characters in SQL statements and automatically converts them to lowercase for execution. Therefore, the user's case-sensitive strings and passwords need to be enclosed in single quotation marks.
Avoid using BINARY type to save non-ASCII type strings, which will easily lead to errors such as garbled data. The correct way is to use NCHAR type to save Chinese characters.
The numerical values in SQL statements are treated as floating or integer numbers, depends on if the value contains decimal point or is in scientific notation format. Therefore, caution is needed since overflow might happen for corresponding data types. E.g., 9999999999999999999 is overflowed as the number is greater than the largest integer number. However, 9999999999999999999.0 is treated as a valid floating number.

Database Management

Create a Database

  CREATE DATABASE [IF NOT EXISTS] db_name [KEEP keep] [DAYS days] [UPDATE 1];

Note:

KEEP is how long the data of the database is kept, the default is 3650 days (10 years), and the database will automatically delete the data expired;
UPDATE marks the database support updating the same timestamp data;
Maximum length of the database name is 33;
Maximum length of a SQL statement is 65480 characters;
Database has more storage-related configuration parameters, see Server-side Configuration .

Show current system parameters
```
SHOW VARIABLES;
```
Use a database
```
USE db_name;
```
Use/switch database (Invalid when accessing through RESTful connection)
Drop a database
```
DROP DATABASE [IF EXISTS] db_name;
```
Delete a database, all data tables included will be deleted. Please use with caution.
Modify database parameters
```
ALTER DATABASE db_name COMP 2;
```
COMP parameter modifies the database file compression flag bit, with the default value of 2 and the value range is [0, 2]. 0 means no compression, 1 means one-stage compression, and 2 means two-stage compression.
```
ALTER DATABASE db_name REPLICA 2;
```
REPLICA parameter refers to the number of replicas of the modified database, and the value range is [1, 3]. For use in a cluster, the number of replicas must be less than or equal to the number of DNODE.
```
ALTER DATABASE db_name KEEP 365;
```
The KEEP parameter refers to the number of days to save a modified data file. The default value is 3650, and the value range is [days, 365000]. It must be greater than or equal to the days parameter value.
```
ALTER DATABASE db_name QUORUM 2;
```
QUORUM parameter refers to the number of confirmations required for successful data writing, and the value range is [1, 3]. For asynchronous replication, quorum is set to 1, and the virtual node with master role can confirm it by itself. For synchronous replication, it needs to be at least 2 or greater. In principle, Quorum > = 1 and Quorum < = replica number, which is required when starting a synchronization module instance.
```
ALTER DATABASE db_name BLOCKS 100;
```
BLOCKS parameter is the number of cache-sized memory blocks in each VNODE (TSDB), so the memory size used for a VNODE equals roughly (cache * blocks). Value range is [3,1000].
```
ALTER DATABASE db_name CACHELAST 0;
```
CACHELAST parameter controls whether last_row of the data subtable is cached in memory. The default value is 0, and the value range is [0, 1]. Where 0 means not enabled and 1 means enabled. (supported from version 2.0. 11)

Tips: After all the above parameters are modified, show databases can be used to confirm whether the modification is successful.
Show all databases in system
```
SHOW DATABASES;
```

Table Management

Create a table
```
CREATE TABLE [IF NOT EXISTS] tb_name (timestamp_field_name TIMESTAMP, field1_name data_type1 [, field2_name data_type2 ...]);
```
Note:
1. The first field must be a timestamp, and system will set it as the primary key;
2. The max length of table name is 192;
3. The length of each row of the table cannot exceed 48K (it's 16K prior to 2.1.7.0) characters;
4. Sub-table names can only consist of letters, numbers, and underscores, and cannot begin with numbers
5. If the data type binary or nchar is used, the maximum number of bytes should be specified, such as binary (20), which means 20 bytes;
Create a table via STable
```
CREATE TABLE [IF NOT EXISTS] tb_name USING stb_name TAGS (tag_value1, ...);
```
Use a STable as template and assign tag values to create a data table.
Create a data table using STable as a template and specify a specific tags column
```
CREATE TABLE [IF NOT EXISTS] tb_name USING stb_name (tag_name1, ...) TAGS (tag_value1, ...);
```
Using the specified STable as a template, specify the values of some tags columns to create a data table. (Unspecified tags columns are set to null values.) Note: This method has been supported since version 2.0. 17. In previous versions, tags columns were not allowed to be specified, but the values of all tags columns must be explicitly given.
Create tables in batches
```
CREATE TABLE [IF NOT EXISTS] tb_name1 USING stb_name TAGS (tag_value1, ...) [IF NOT EXISTS] tb_name2 USING stb_name TAGS (tag_value2, ...) ...;
```
Create a large number of data tables in batches faster. (Server side 2.0. 14 and above)

Note:
1. The method of batch creating tables requires that the data table must use STable as a template.
2. On the premise of not exceeding the length limit of SQL statements, it is suggested that the number of tables in a single statement should be controlled between 1000 and 3000, which will obtain an ideal speed of table creating.
Drop a table
```
DROP TABLE [IF EXISTS] tb_name;
```
Show all data table information under the current database
```
SHOW TABLES [LIKE tb_name_wildcard];
```
Show all data table information under the current database. Note: Wildcard characters can be used to match names in like. The maximum length of this wildcard character string cannot exceed 24 bytes. Wildcard matching: 1) '%' (percent sign) matches 0 to any number of characters; 2) '_' underscore matches one character.
Modify display character width online
```
SET MAX_BINARY_DISPLAY_WIDTH <nn>;
```
Get schema information of a table
```
DESCRIBE tb_name;
```
Add a column to table
```
ALTER TABLE tb_name ADD COLUMN field_name data_type;
```
Note:
1. The maximum number of columns is 1024 and the minimum number is 2;
2. The maximum length of a column name is 64;
Drop a column in table
```
ALTER TABLE tb_name DROP COLUMN field_name; 
```
If the table is created through a STable, the operation of table schema changing can only be carried out on the STable. Moreover, the schema changes for the STable take effect for all tables created through the schema. For tables that are not created through STables, you can modify the table schema directly.

STable Management

Note: In 2.0.15.0 and later versions, STABLE reserved words are supported. That is, in the instruction description later in this section, the three instructions of CREATE, DROP and ALTER need to write TABLE instead of STABLE in the old version as the reserved word.

Create a STable
```
CREATE STABLE [IF NOT EXISTS] stb_name (timestamp_field_name TIMESTAMP, field1_name data_type1 [, field2_name data_type2 ...]) TAGS (tag1_name tag_type1, tag2_name tag_type2 [, tag3_name tag_type3]);
```
Similar to a standard table creation SQL, but you need to specify name and type of TAGS field.

Note:
1. Data types of TAGS column cannot be timestamp;
2. No duplicated TAGS column names;
3. Reversed word cannot be used as a TAGS column name;
4. The maximum number of TAGS is 128, and at least 1 TAG allowed, with a total length of no more than 16K characters.
Drop a STable
```
DROP STABLE [IF EXISTS] stb_name;
```
Drop a STable automatically deletes all sub-tables created through the STable.
Show all STable information under the current database
```
SHOW STABLES [LIKE tb_name_wildcard];
```
View all STables under the current database and relevant information, including name, creation time, column number, tag number, number of tables created through the STable, etc.
Obtain schema information of a STable
```
DESCRIBE stb_name;
```

Add column to STable

ALTER STABLE stb_name ADD COLUMN field_name data_type;

Drop column in STable

ALTER STABLE stb_name DROP COLUMN field_name;

TAG Management in STable

Add a tag
```
ALTER STABLE stb_name ADD TAG new_tag_name tag_type;
```
Add a new tag to the STable and specify a type of the new tag. The total number of tags cannot exceed 128 and the total length does not exceed 16K characters.
Drop a tag
```
ALTER STABLE stb_name DROP TAG tag_name;
```
Delete a tag of STable. After deleting the tag, all sub-tables under the STable will also automatically delete the same tag.
Modify a tag name
```
ALTER STABLE stb_name CHANGE TAG old_tag_name new_tag_name;
```
Modify a tag name of STable. After modifying, all sub-tables under the STable will automatically update the new tag name.
Modify a tag value of sub-table
```
ALTER TABLE tb_name SET TAG tag_name=new_tag_value;
```
Note: Except that the operation of tag value updating is carried out for sub-tables, all other tag operations (adding tags, deleting tags, etc.) can only be applied to STable, and cannot be operated on a single sub-table. After adding a tag to a STable, all tables established based on that will automatically add a new tag, and the default value is NULL.

Data Writing

Insert a record
```
INSERT INTO tb_name VALUES (field_value, ...);
```
Insert a record into table tb_name.
Insert a record with data corresponding to a given column
```
INSERT INTO tb_name (field1_name, ...) VALUES (field1_value1, ...);
```
Insert a record into table tb_name, and the data corresponds to a given column. For columns that do not appear in the SQL statement, database will automatically populate them with NULL. Primary key (timestamp) cannot be NULL.

Insert multiple records

INSERT INTO tb_name VALUES (field1_value1, ...) (field1_value2, ...) ...;

Insert multiple records into table tb_name.

Insert multiple records into a given column
```
INSERT INTO tb_name (field1_name, ...) VALUES (field1_value1, ...) (field1_value2, ...) ...;
```
Insert multiple records into a given column of table tb_name.

Insert multiple records into multiple tables

INSERT INTO tb1_name VALUES (field1_value1, ...) (field1_value2, ...) ...
            tb2_name VALUES (field1_value1, ...) (field1_value2, ...) ...;

Insert multiple records into tables tb1_name and tb2_name at the same time.

Insert multiple records per column into multiple tables
```
INSERT INTO tb1_name (tb1_field1_name, ...) VALUES (field1_value1, ...) (field1_value2, ...) ...
            tb2_name (tb2_field1_name, ...) VALUES (field1_value1, ...) (field1_value2, ...) ...;
```
Insert multiple records per column into tables tb1_name and tb2_name at the same time. Note: The timestamp of the oldest record allowed to be inserted is relative to the current server time, minus the configured keep value (days of data retention), and the timestamp of the latest record allowed to be inserted is relative to the current server time, plus the configured days value (interval of data storage in the data file, in days). Both keep and days can be specified when the database is created, and the default values are 3650 days and 10 days, respectively.
Automatically create a table when inserting
```
INSERT INTO tb_name USING stb_name TAGS (tag_value1, ...) VALUES (field_value1, ...);
```
If user is not sure whether a table exists when writing data, the automatic table building syntax can be used to create a non-existent table when writing. If the table already exists, no new table will be created. When automatically creating a table, it is required to use the STable as a template and specify tags value for the data table.
Automatically create a table when inserting, and specify a given tags column
```
INSERT INTO tb_name USING stb_name (tag_name1, ...) TAGS (tag_value1, ...) VALUES (field_value1, ...);
```
During automatic table creation, only the values of some tags columns can be specified, and the unspecified tags columns will be null.

History writing: The IMPORT or INSERT command can be used. The syntax and function of IMPORT are exactly the same as those of INSERT.

Note: For SQL statements in insert type, the stream parsing strategy we adopt will still execute the correct part of SQL before the following errors are found. In the following sql, insert statement is invalid, but d1001 will still be created.

taos> CREATE TABLE meters(ts TIMESTAMP, current FLOAT, voltage INT, phase FLOAT) TAGS(location BINARY(30), groupId INT);
Query OK, 0 row(s) affected (0.008245s)

taos> SHOW STABLES;
              name              |      created_time       | columns |  tags  |   tables    |
============================================================================================
 meters                         | 2020-08-06 17:50:27.831 |       4 |      2 |           0 |
Query OK, 1 row(s) in set (0.001029s)

taos> SHOW TABLES;
Query OK, 0 row(s) in set (0.000946s)

taos> INSERT INTO d1001 USING meters TAGS('Beijing.Chaoyang', 2) VALUES('a');

DB error: invalid SQL: 'a' (invalid timestamp) (0.039494s)

taos> SHOW TABLES;
           table_name           |      created_time       | columns |          stable_name           |
======================================================================================================
 d1001                          | 2020-08-06 17:52:02.097 |       4 | meters                         |
Query OK, 1 row(s) in set (0.001091s)

Data Query

Query Syntax:

SELECT select_expr [, select_expr ...]
    FROM {tb_name_list}
    [WHERE where_condition]
    [INTERVAL (interval_val [, interval_offset])]
    [SLIDING sliding_val]
    [FILL fill_val]
    [GROUP BY col_list]
    [ORDER BY col_list { DESC | ASC }]
    [SLIMIT limit_val [SOFFSET offset_val]]
    [LIMIT limit_val [OFFSET offset_val]]
    [>> export_file];

SELECT Clause

A select clause can be a sub-query of UNION and another query.

Wildcard character

The wildcard * can be used to refer to all columns. For ordinary tables, there’re only ordinary columns in results.

taos> SELECT * FROM d1001;
           ts            |       current        |   voltage   |        phase         |
======================================================================================
 2018-10-03 14:38:05.000 |             10.30000 |         219 |              0.31000 |
 2018-10-03 14:38:15.000 |             12.60000 |         218 |              0.33000 |
 2018-10-03 14:38:16.800 |             12.30000 |         221 |              0.31000 |
Query OK, 3 row(s) in set (0.001165s)

For STables, wildcards contain tag columns.

taos> SELECT * FROM meters;
           ts            |       current        |   voltage   |        phase         |            location            |   groupid   |
=====================================================================================================================================
 2018-10-03 14:38:05.500 |             11.80000 |         221 |              0.28000 | Beijing.Haidian                |           2 |
 2018-10-03 14:38:16.600 |             13.40000 |         223 |              0.29000 | Beijing.Haidian                |           2 |
 2018-10-03 14:38:05.000 |             10.80000 |         223 |              0.29000 | Beijing.Haidian                |           3 |
 2018-10-03 14:38:06.500 |             11.50000 |         221 |              0.35000 | Beijing.Haidian                |           3 |
 2018-10-03 14:38:04.000 |             10.20000 |         220 |              0.23000 | Beijing.Chaoyang               |           3 |
 2018-10-03 14:38:16.650 |             10.30000 |         218 |              0.25000 | Beijing.Chaoyang               |           3 |
 2018-10-03 14:38:05.000 |             10.30000 |         219 |              0.31000 | Beijing.Chaoyang               |           2 |
 2018-10-03 14:38:15.000 |             12.60000 |         218 |              0.33000 | Beijing.Chaoyang               |           2 |
 2018-10-03 14:38:16.800 |             12.30000 |         221 |              0.31000 | Beijing.Chaoyang               |           2 |
Query OK, 9 row(s) in set (0.002022s)

Wildcards support table name prefixes, the two following SQL statements will return all columns:

SELECT * FROM d1001;
SELECT d1001.* FROM d1001;

In Join query, the results returned by * with prefix and * without prefix are different. * returns all column data of all tables (excluding tags), while wildcards with prefix only return column data of the corresponding table.

taos> SELECT * FROM d1001, d1003 WHERE d1001.ts=d1003.ts;
           ts            | current |   voltage   |    phase     |           ts            | current |   voltage   |    phase     |
==================================================================================================================================
 2018-10-03 14:38:05.000 | 10.30000|         219 |      0.31000 | 2018-10-03 14:38:05.000 | 10.80000|         223 |      0.29000 |
Query OK, 1 row(s) in set (0.017385s)

taos> SELECT d1001.* FROM d1001,d1003 WHERE d1001.ts = d1003.ts;
           ts            |       current        |   voltage   |        phase         |
======================================================================================
 2018-10-03 14:38:05.000 |             10.30000 |         219 |              0.31000 |
Query OK, 1 row(s) in set (0.020443s)

In the process of using SQL functions for query, some SQL functions support wildcard operation. The difference is that the count(\*) function returns only one column, but the first,last,last_row functions return all columns.

taos> SELECT COUNT(*) FROM d1001;
       count(*)        |
========================
                     3 |
Query OK, 1 row(s) in set (0.001035s)

taos> SELECT FIRST(*) FROM d1001;
        first(ts)        |    first(current)    | first(voltage) |     first(phase)     |
=========================================================================================
 2018-10-03 14:38:05.000 |             10.30000 |            219 |              0.31000 |
Query OK, 1 row(s) in set (0.000849s)

Tag Column

Since version 2.0. 14, it is supported to specify tag column in queries of ordinary tables, and the values of tag columns will be returned together with the data of other ordinary columns.

taos> SELECT location, groupid, current FROM d1001 LIMIT 2;
            location            |   groupid   |       current        |
======================================================================
 Beijing.Chaoyang               |           2 |             10.30000 |
 Beijing.Chaoyang               |           2 |             12.60000 |
Query OK, 2 row(s) in set (0.003112s)

Note: The wildcard * of ordinary tables does not contain tag columns.

Obtain the de-duplicated value of a tag column

Since version 2.0. 15, it is supported to specify DISTINCT keyword when querying tag columns in STables, which will return all non-duplicate values of given tag columns.

SELECT DISTINCT tag_name FROM stb_name;

Note: At present, DISTINCT keyword only supports deduplication of tag columns of STables, and cannot be used for ordinary columns.

Column name in result set

In SELECT clause, if there’s no returning of column name in result set, the result set column name defaults to the expression name in SELECT clause as the column name. In addition, user can use AS to rename the columns in the returned result set. For example:

taos> SELECT ts, ts AS primary_key_ts FROM d1001;
           ts            |     primary_key_ts      |
====================================================
 2018-10-03 14:38:05.000 | 2018-10-03 14:38:05.000 |
 2018-10-03 14:38:15.000 | 2018-10-03 14:38:15.000 |
 2018-10-03 14:38:16.800 | 2018-10-03 14:38:16.800 |
Query OK, 3 row(s) in set (0.001191s)

However, renaming for one single column is not supported for first(*),last(*),last_row(*).

Implicit result column

Select_exprs can be the name of a column belongs to a table, or it can be a column-based functional expression or calculation formula, with an upper limit of 256. When user uses interval or group by tags clause, the timestamp column (the first column) and the tag column in group by clause are forced to be returned in the final returned result. Later versions can support turning off the output of implicit columns in group by clause, and the column output is completely controlled by select clause.

List of STable

The FROM keyword can be followed by a list of several tables (STables) or result of a sub-query.

If you do not specify user's current database, you can use the database name before the table name to specify the database to which the table belongs. For example: power.d1001 to use tables across databases.

SELECT * FROM power.d1001;
------------------------------
USE power;
SELECT * FROM d1001;

Special Functions

Some special query functions can be performed without using FROM clause. Obtain the current database database ():

taos> SELECT DATABASE();
           database()           |
=================================
 power                          |
Query OK, 1 row(s) in set (0.000079s)

If no default database is specified when logging in, and USE command is not used to switch data, then NULL is returned.

taos> SELECT DATABASE();
           database()           |
=================================
 NULL                           |
Query OK, 1 row(s) in set (0.000184s)

Get server and client version numbers:

taos> SELECT CLIENT_VERSION();
 client_version() |
===================
 2.0.0.0          |
Query OK, 1 row(s) in set (0.000070s)

taos> SELECT SERVER_VERSION();
 server_version() |
===================
 2.0.0.0          |
Query OK, 1 row(s) in set (0.000077s)

A server state detection statement. If server is normal, return a number (for example, 1). If server is exceptional, return error code. The SQL syntax can be compatible with the check of TDengine status by connection pool and the check of database server status by third-party tools. And can avoid connection loss of connection pool caused by using a wrong heartbeat detection SQL statement.

taos> SELECT SERVER_STATUS();
 server_status() |
==================
               1 |
Query OK, 1 row(s) in set (0.000074s)

taos> SELECT SERVER_STATUS() AS status;
   status    |
==============
           1 |
Query OK, 1 row(s) in set (0.000081s)

Special keywords in TAOS SQL

TBNAME: It can be regarded as a special tag in a STable query, representing the name of sub-table involved in the query

_c0: Represents the first column of a table (STable) _qstart,_qstop,_qduration: Represents starting time/stopping time/duration of query time window filter in where condition (supported since 2.6.0.0） _wstart,_wstop,_wduration: Used in time-dimension aggregation query(e.g. interval/session window/state window）to represent starting time/stopping time/duration of each generated time window (supported since 2.6.0.0)

Tips

Get all sub-table names and related tags information of a STable:

SELECT TBNAME, location FROM meters;

Statistics of sub-tables number under a STable:

SELECT COUNT(TBNAME) FROM meters;

The two queries above only support adding filters for TAGS in Where conditional clause. For example:

taos> SELECT TBNAME, location FROM meters;
             tbname             |            location            |
==================================================================
 d1004                          | Beijing.Haidian                |
 d1003                          | Beijing.Haidian                |
 d1002                          | Beijing.Chaoyang               |
 d1001                          | Beijing.Chaoyang               |
Query OK, 4 row(s) in set (0.000881s)

taos> SELECT COUNT(tbname) FROM meters WHERE groupId > 2;
     count(tbname)     |
========================
                     2 |
Query OK, 1 row(s) in set (0.001091s)

You can use * to return all columns, or given column names. Four operations can be performed on numeric columns, and column names can be given to output columns.
WHERE statement can use various logical decisions to filter numeric values, or wildcards to filter strings
The output is sorted by default in ascending order by timestamps in the first column, but you can specify descending order (_c0 refers to the first column timestamp). It is illegal to use ORDER BY to sort other fields.
Parameter LIMIT controls the number of outputs, and OFFSET specifies which output starts from. LIMIT/OFFSET executes the result set after ORDER BY.
"> >" output can be exported to a specified file

Supported Filtering Operations

Operation	Note	Applicable Data Types
>	larger than	timestamp and all numeric types
<	smaller than	timestamp and all numeric types
>=	larger than or equal to	timestamp and all numeric types
<=	smaller than or equal to	timestamp and all numeric types
=	equal to	all types
<>	not equal to	all types
between and	within a certain range	timestamp and all numeric types
%	match with any char sequences	binary nchar
_	match with a single char	binary nchar

To filter the range of multiple fields at the same time, you need to use keyword AND to connect different query conditions. The query filtering between different columns connected by OR are not supported at the moment.
For filtering a single field, if it is a time filtering condition, only one condition in a statement can be set; however, for other (ordinary) columns or tag columns, OR keyword can be used for query filtering of combined conditions. For example: ((value > 20 AND value < 30) OR (value < 12)).
Since version 2.0. 17, condition filtering supports BETWEEN AND syntax. For example, WHERE col2 BETWEEN 1.5 AND 3.25 means that the query condition is "1.5 ≤ col2 ≤ 3.25".

SQL Example

For example, table tb1 is created with the following statement

CREATE TABLE tb1 (ts TIMESTAMP, col1 INT, col2 FLOAT, col3 BINARY(50));

Query all records of the last hour of tb1
```
SELECT * FROM tb1 WHERE ts >= NOW - 1h;
```
Look up table tb1 from 2018-06-01 08:00:00. 000 to 2018-06-02 08:00:00. 000, and col3 string is a record ending in 'nny ', and the result is in descending order of timestamp:
```
SELECT * FROM tb1 WHERE ts > '2018-06-01 08:00:00.000' AND ts <= '2018-06-02 08:00:00.000' AND col3 LIKE '%nny' ORDER BY ts DESC;
```
Query the sum of col1 and col2, and name it complex. The time is greater than 2018-06-01 08:00:00. 000, and col2 is greater than 1.2. As a result, only 10 records are outputted, starting from item 5
```
SELECT (col1 + col2) AS 'complex' FROM tb1 WHERE ts > '2018-06-01 08:00:00.000' AND col2 > 1.2 LIMIT 10 OFFSET 5;
```
Query the records of past 10 minutes, the value of col2 is greater than 3.14, and output the result to the file /home/testoutput.csv.
```
SELECT COUNT(*) FROM tb1 WHERE ts >= NOW - 10m AND col2 > 3.14 >> /home/testoutput.csv;
```

SQL Functions

TDengine supports aggregations over data, they are listed below:

COUNT

SELECT COUNT([*|field_name]) FROM tb_name [WHERE clause];

Function: record the number of rows or non-null values in a column of statistics/STable.

Returned result data type: long integer INT64.

Applicable Fields: Applied to all fields.

Applied to: table, STable.

Note:

You can use * instead of specific fields, and use *() to return the total number of records.
The query results for fields of the same table (excluding NULL values) are the same.
If the statistic object is a specific column, return the number of records with non-NULL values in that column.

Example:

taos> SELECT COUNT(*), COUNT(voltage) FROM meters;
    count(*)        |    count(voltage)     |
================================================
                    9 |                     9 |
Query OK, 1 row(s) in set (0.004475s)

taos> SELECT COUNT(*), COUNT(voltage) FROM d1001;
    count(*)        |    count(voltage)     |
================================================
                    3 |                     3 |
Query OK, 1 row(s) in set (0.001075s)

AVG

SELECT AVG(field_name) FROM tb_name [WHERE clause];

Function: return the average value of a column in statistics/STable.

Return Data Type: double.

Applicable Fields: all types except timestamp, binary, nchar, bool.

Applied to: table,STable.

Example:

taos> SELECT AVG(current), AVG(voltage), AVG(phase) FROM meters;
  avg(current)        |       avg(voltage)        |        avg(phase)         |
====================================================================================
          11.466666751 |             220.444444444 |               0.293333333 |
Query OK, 1 row(s) in set (0.004135s)

taos> SELECT AVG(current), AVG(voltage), AVG(phase) FROM d1001;
  avg(current)        |       avg(voltage)        |        avg(phase)         |
====================================================================================
          11.733333588 |             219.333333333 |               0.316666673 |
Query OK, 1 row(s) in set (0.000943s)

TWA
```
SELECT TWA(field_name) FROM tb_name WHERE clause;
```
Function: Time weighted average function. The time-weighted average of a column in a statistical table over a period of time.

Return Data Type: double.

Applicable Fields: all types except timestamp, binary, nchar, bool.

Applied to: table.

SUM

SELECT SUM(field_name) FROM tb_name [WHERE clause];

Function: return the sum of a statistics/STable.

Return Data Type: INT64 and Double.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Applied to: table,STable.

Example:

taos> SELECT SUM(current), SUM(voltage), SUM(phase) FROM meters;
  sum(current)        |     sum(voltage)      |        sum(phase)         |
================================================================================
          103.200000763 |                  1984 |               2.640000001 |
Query OK, 1 row(s) in set (0.001702s)

taos> SELECT SUM(current), SUM(voltage), SUM(phase) FROM d1001;
  sum(current)        |     sum(voltage)      |        sum(phase)         |
================================================================================
          35.200000763 |                   658 |               0.950000018 |
Query OK, 1 row(s) in set (0.000980s)

STDDEV
```
SELECT STDDEV(field_name) FROM tb_name [WHERE clause];
```
Function: Mean square deviation of a column in statistics table.

Return Data Type: Double.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Applied to: table. (also support STable since version 2.0.15.1)

Example:
```
taos> SELECT STDDEV(current) FROM d1001;
  stddev(current)      |
============================
          1.020892909 |
Query OK, 1 row(s) in set (0.000915s)
```
LEASTSQUARES
```
SELECT LEASTSQUARES(field_name, start_val, step_val) FROM tb_name [WHERE clause];
```
Function: Value of a column in statistical table is a fitting straight equation of primary key (timestamp). Start_val is the initial value of independent variable, and step_val is the step size value of independent variable.

Return Data Type: String expression (slope, intercept).

Applicable Fields: All types except timestamp, binary, nchar, bool.

Note: Independent variable is the timestamp, and dependent variable is the value of the column.

Applied to: table.

Example:
```
taos> SELECT LEASTSQUARES(current, 1, 1) FROM d1001;
            leastsquares(current, 1, 1)             |
=====================================================
{slop:1.000000, intercept:9.733334}                 |
Query OK, 1 row(s) in set (0.000921s)
```
MODE
```
SELECT MODE(field_name) FROM tb_name [WHERE clause];
```
Function: Returns the value with the highest frequency. If there are multiple highest values with the same frequency, the output is NULL.

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp.

Supported version: Version after 2.6.0 .

Note: Since the amount of returned data is unknown, considering the memory factor, in order to return the result normally, it is recommended that the amount of non repeated data is 100000, otherwise an error will be reported.

Example:
```
taos> select voltage from d002;
    voltage        |
========================
       1           |
       1           |
       2           |
       19          |
Query OK, 4 row(s) in set (0.003545s)

taos> select mode(voltage) from d002;
  mode(voltage)    |
========================
       1           |
Query OK, 1 row(s) in set (0.019393s)
```
HYPERLOGLOG
```
SELECT HYPERLOGLOG(field_name) FROM { tb_name | stb_name } [WHERE clause];
```
Function:
- The hyperloglog algorithm is used to return the cardinality of a column. In the case of large amount of data, the algorithm can significantly reduce the occupation of memory, but the cardinality is an estimated value, and the standard error(the standard error is the standard deviation of the average of multiple experiments, not the error with the real result) is 0.81%.
- When the amount of data is small, the algorithm is not very accurate. You can use the method like this: select count(data) from (select unique(col) as data from table).
Return Data Type:Integer.

Applicable Fields: All types.

Supported version: Version after 2.6.0 .

Example:
```
taos> select dbig from shll;
     dbig          |
========================
       1           |
       1           |
       1           |
       NULL        |
       2           |
       19          |
       NULL        |
       9           |
Query OK, 8 row(s) in set (0.003755s)

taos> select hyperloglog(dbig) from shll;
  hyperloglog(dbig)|
========================
       4           |
Query OK, 1 row(s) in set (0.008388s)
```

Selector Functions

MIN

SELECT MIN(field_name) FROM {tb_name | stb_name} [WHERE clause];

Function: return the minimum value of a specific column in statistics/STable.

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Example:

taos> SELECT MIN(current), MIN(voltage) FROM meters;
    min(current)     | min(voltage) |
======================================
            10.20000 |          218 |
Query OK, 1 row(s) in set (0.001765s)

taos> SELECT MIN(current), MIN(voltage) FROM d1001;
    min(current)     | min(voltage) |
======================================
            10.30000 |          218 |
Query OK, 1 row(s) in set (0.000950s)

MAX

SELECT MAX(field_name) FROM { tb_name | stb_name } [WHERE clause];

Function: return the maximum value of a specific column in statistics/STable.

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Example:

taos> SELECT MAX(current), MAX(voltage) FROM meters;
   max(current)     | max(voltage) |
======================================
           13.40000 |          223 |
Query OK, 1 row(s) in set (0.001123s)

taos> SELECT MAX(current), MAX(voltage) FROM d1001;
   max(current)     | max(voltage) |
======================================
           12.60000 |          221 |
Query OK, 1 row(s) in set (0.000987s)

FIRST

SELECT FIRST(field_name) FROM { tb_name | stb_name } [WHERE clause];

Function: The first non-NULL value written into a column in statistics/STable.

Return Data Type: Same as applicable fields.

Applicable Fields: All types.

Note:

To return the first (minimum timestamp) non-NULL value of each column, use FIRST (*);
if all columns in the result set are NULL values, the return result of the column is also NULL;
If all columns in the result set are NULL values, no result is returned.

Example:

taos> SELECT FIRST(*) FROM meters;
      first(ts)        |    first(current)    | first(voltage) |     first(phase)     |
=========================================================================================
2018-10-03 14:38:04.000 |             10.20000 |            220 |              0.23000 |
Query OK, 1 row(s) in set (0.004767s)

taos> SELECT FIRST(current) FROM d1002;
     first(current)    |
=======================
            10.20000 |
Query OK, 1 row(s) in set (0.001023s)

LAST

SELECT LAST(field_name) FROM { tb_name | stb_name } [WHERE clause];

Function: The last non-NULL value written by the value of a column in statistics/STable.

Return Data Type: Same as applicable fields.

Applicable Fields: All types.

Note:

To return the last (maximum timestamp) non-NULL value of each column, use LAST (*);
If a column in the result set has a NULL value, the returned result of the column is also NULL; if all columns in the result set have NULL values, no result is returned.

Example:

taos> SELECT LAST(*) FROM meters;
        last(ts)         |    last(current)     | last(voltage) |     last(phase)      |
========================================================================================
2018-10-03 14:38:16.800 |             12.30000 |           221 |              0.31000 |
Query OK, 1 row(s) in set (0.001452s)

taos> SELECT LAST(current) FROM d1002;
    last(current)     |
=======================
            10.30000 |
Query OK, 1 row(s) in set (0.000843s)

TOP

SELECT TOP(field_name, K) FROM { tb_name | stb_name } [WHERE clause];

Function: The top k non-NULL values of a column in statistics/STable. If there are more than k column values tied for the largest, the one with smaller timestamp is returned.

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Note:

The range of k value is 1≤k≤100;
System also returns the timestamp column associated with the record.

Example:

taos> SELECT TOP(current, 3) FROM meters;
        ts            |   top(current, 3)    |
=================================================
2018-10-03 14:38:15.000 |             12.60000 |
2018-10-03 14:38:16.600 |             13.40000 |
2018-10-03 14:38:16.800 |             12.30000 |
Query OK, 3 row(s) in set (0.001548s)

taos> SELECT TOP(current, 2) FROM d1001;
        ts            |   top(current, 2)    |
=================================================
2018-10-03 14:38:15.000 |             12.60000 |
2018-10-03 14:38:16.800 |             12.30000 |
Query OK, 2 row(s) in set (0.000810s)

BOTTOM

SELECT BOTTOM(field_name, K) FROM { tb_name | stb_name } [WHERE clause];

Function: The last k non-NULL values of a column in statistics/STable. If there are more than k column values tied for the smallest, the one with smaller timestamp is returned.

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Note:

The range of k value is 1≤k≤100;
System also returns the timestamp column associated with the record.

Example:

taos> SELECT BOTTOM(voltage, 2) FROM meters;
        ts            | bottom(voltage, 2) |
===============================================
2018-10-03 14:38:15.000 |                218 |
2018-10-03 14:38:16.650 |                218 |
Query OK, 2 row(s) in set (0.001332s)

taos> SELECT BOTTOM(current, 2) FROM d1001;
        ts            |  bottom(current, 2)  |
=================================================
2018-10-03 14:38:05.000 |             10.30000 |
2018-10-03 14:38:16.800 |             12.30000 |
Query OK, 2 row(s) in set (0.000793s)

PERCENTILE
```
SELECT PERCENTILE(field_name, P) FROM { tb_name } [WHERE clause];
```
Function: Percentile of the value of a column in statistical table.

Return Data Type: Double.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Note: The range of P value is 0 ≤ P ≤ 100. P equals to MIN when, and equals MAX when it’s 100.

Example:
```
taos> SELECT PERCENTILE(current, 20) FROM d1001;
percentile(current, 20)  |
============================
            11.100000191 |
Query OK, 1 row(s) in set (0.000787s)
```
APERCENTILE
```
SELECT APERCENTILE(field_name, P) FROM { tb_name | stb_name } [WHERE clause];
```
Function: The value percentile of a column in statistical table is similar to the PERCENTILE function, but returns approximate results.

Return Data Type: Double.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Note: The range of P value is 0 ≤ P ≤ 100. P equals to MIN when, and equals MAX when it’s 100. APERCENTILE function is recommended, which performs far better than PERCENTILE function.

LAST_ROW

SELECT LAST_ROW(field_name) FROM { tb_name | stb_name };

Function: Return the last record of a table (STtable).

Return Data Type: Double.

Applicable Fields: All types.

Note: Unlike last function, last_row does not support time range restriction and forces the last record to be returned.

Example:

taos> SELECT LAST_ROW(current) FROM meters;
last_row(current)   |
=======================
            12.30000 |
Query OK, 1 row(s) in set (0.001238s)

taos> SELECT LAST_ROW(current) FROM d1002;
last_row(current)   |
=======================
            10.30000 |
  Query OK, 1 row(s) in set (0.001042s)

TAIL

SELECT TAIL(field_name, k, offset_val) FROM {tb_name | stb_name} [WHERE clause];

Function: Skip the last num of offset_value, return the k consecutive records without ignoring NULL value. offset_val can be empty, then the last K records are returned.The function is equivalent to:order by ts desc LIMIT k OFFSET offset_val.

Range：k: [1,100] offset_val: [0,100]。

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp.

Applied to: table stable.

Supported version: Version after 2.6.0 .

Example:


taos> select ts,dbig from tail2;
       ts            |         dbig          |
==================================================
2021-10-15 00:31:33.000 |                     1 |
2021-10-17 00:31:31.000 |                  NULL |
2021-12-24 00:31:34.000 |                     2 |
2022-01-01 08:00:05.000 |                    19 |
2022-01-01 08:00:06.000 |                  NULL |
2022-01-01 08:00:07.000 |                     9 |
Query OK, 6 row(s) in set (0.001952s)

taos> select tail(dbig,2,2) from tail2;
ts                      |    tail(dbig,2,2)     |
==================================================
2021-12-24 00:31:34.000 |                     2 |
2022-01-01 08:00:05.000 |                    19 |
Query OK, 2 row(s) in set (0.002307s)

UNIQUE

SELECT UNIQUE(field_name) FROM {tb_name | stb_name} [WHERE clause];

Function: Returns the first occurrence of a value in this column.

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp.

Applied to: table stable.

Supported version: Version after 2.6.0 .

Note:

This function can be applied to ordinary tables and super tables. Cannot be used with window operations，such as interval/state_window/session_window.
Since the amount of returned data is unknown, considering the memory factor, in order to return the result normally, it is recommended that the amount of non repeated data is 100000, otherwise an error will be reported.

Example:


taos> select ts,voltage from unique1;
       ts            |        voltage        |
==================================================
2021-10-17 00:31:31.000 |                     1 |
2022-01-24 00:31:31.000 |                     1 |
2021-10-17 00:31:31.000 |                     1 |
2021-12-24 00:31:31.000 |                     2 |
2022-01-01 08:00:01.000 |                    19 |
2021-10-17 00:31:31.000 |                  NULL |
2022-01-01 08:00:02.000 |                  NULL |
2022-01-01 08:00:03.000 |                     9 |
Query OK, 8 row(s) in set (0.003018s)

taos> select unique(voltage) from unique1;
ts                      |    unique(voltage)    |
==================================================
2021-10-17 00:31:31.000 |                     1 |
2021-10-17 00:31:31.000 |                  NULL |
2021-12-24 00:31:31.000 |                     2 |
2022-01-01 08:00:01.000 |                    19 |
2022-01-01 08:00:03.000 |                     9 |
Query OK, 5 row(s) in set (0.108458s)

Computing Functions

DIFF
```
SELECT DIFF(field_name) FROM tb_name [WHERE clause];
```
Function: Return the value difference between a column and the previous column.

Return Data Type: Same as applicable fields.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Note: The number of output result lines is the total number of lines in the range minus one, and there is no result output in the first line.

Example:
```
taos> SELECT DIFF(current) FROM d1001;
        ts            |    diff(current)     |
=================================================
2018-10-03 14:38:15.000 |              2.30000 |
2018-10-03 14:38:16.800 |             -0.30000 |
Query OK, 2 row(s) in set (0.001162s)
```

SPREAD

SELECT SPREAD(field_name) FROM { tb_name | stb_name } [WHERE clause];

Function: Return the difference between the max value and the min value of a column in statistics /STable.

Return Data Type: Double.

Applicable Fields: All types except binary, nchar, bool.

Note: Applicable for TIMESTAMP field, which indicates the time range of a record.

Example:

taos> SELECT SPREAD(voltage) FROM meters;
    spread(voltage)      |
============================
            5.000000000 |
Query OK, 1 row(s) in set (0.001792s)

taos> SELECT SPREAD(voltage) FROM d1001;
    spread(voltage)      |
============================
            3.000000000 |
Query OK, 1 row(s) in set (0.000836s)

CSUM
```
SELECT CSUM(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Cumulative sum computes the running total of one time series. It occurs in select clause of SQL statement.

Input: Input column data type should be a numeric type.

Output: If the input data type is unsigned int type, the result data type is uint64_t. If the input data type is signed int type, the result data type is int64_t. If the input data type is float or double, the result data type is double. The function also outputs the timestamp of the current row.

Table: The csum function only applies to the normal table, child table, and super table with group by tbname.

Nested Query: The csum function applies to both outer query and nested query.

Note: Can't be used with +-*/ arithmatic operations，like csum(col1) + csum(col2), can only be used with aggragation functions.
MAVG
```
SELECT MAVG(field_name, K) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Moving Average Function Computes the rolling simple average over k values of one time series. It occurs in select clause of SQL statement. If the input time series has less than k values, no result is calculated.

Input: Input column data should be a numeric type.

Output: The Result data type is double. The function also outputs the timestamp of the current row.

Parameter: K is an integer between 1 and 1000.

Table: The mavg function only applies to the normal table, child table, and super table with group by tbname.

Nested Query: The mavg function applies to both outer query and nested query.

Note: Can't be used with +-*/ arithmatic operations, like mavg(col1, k1) + mavg(col2, k1); can only be used with normal columns, selection and projection functions，can't be used with aggragation functions.
SAMPLE
```
SELECT SAMPLE(field_name, K) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Sample function samples k values from a specific time series with equal probability. It occurs in select clause of SQL statement

Input: There are no restrictions on the input data type.

Output: The output data type is the same as the input data type. The function also outputs the timestamp of the current row.

Parameter: K is an integer between 1 and 1000.

Table: he sample function only applies to the normal table, child table, and super table with group by tbname.

Nested Query: The sample function applies to both outer query and nested query.

Note: Can't be used as operand in an expression
ASIN
```
SELECT ASIN(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the arc-sine of the input value.

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
ACOS
```
SELECT ACOS(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the arc-cosine of the input value.

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
ATAN
```
SELECT ATAN(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the arc-tangent of the input value.

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
SIN
```
SELECT SIN(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the sine of the input value.

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
COS
```
SELECT COS(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the cosine of the input value.

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
TAN
```
SELECT TAN(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the tangent of the input value.

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
POW
```
SELECT POW(field_name, power) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the input value raised to the specified power of the second argument

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
LOG
```
SELECT LOG(field_name, base) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the logarithm of the input value with base

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
ABS
```
SELECT ABS(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the absolute value of the input value

Output Data Type: If the input data is an integer numeric value, the output data type is ubigint. If the input data is a float or double value, the output data type is double

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
SQRT
```
SELECT SQRT(field_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the square root value of the input value

Output Data Type: DOUBLE.

Input: applies to value of all types except timestamp, binary, nchar, and bool. Can not apply to tag column of super table.

Embedded Query Support: Both Outer Query and Inner Query

Notes：

If input value is NULL, the output value is NULL.

It is a scalar function and can not be used together with aggregate function

Applies to columns of normal table, child table and super table

Supported after version 2.6.0.x
CAST
```
SELECT CAST(expression AS type_name) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Converts a value into as a specific data type of type_name.

Output Data Type: type_name specified. Supported types include BIGINT, BINARY(N), TIMESTAMP and NCHAR(N) and BIGINT UNSIGNED

Input: Normal column, constant, scalar function and the arithmetic computation(+,-,*,/,%) among them. Input data type includes BOOL, TINYINT, SMALLINT, INT, BIGINT, FLOAT, DOUBLE, BINARY(M), TIMESTAMP, NCHAR(M), TINYINT UNSIGNED, SMALLINT UNSIGNED, INT UNSIGNED, and BIGINT UNSIGNED

Notes:

Reports error for unsupported cast

It is a scalar function and its output is NULL for input NULL

Supported after version 2.6.0.x
CONCAT
```
SELECT CONCAT(str1|column1, str2|column2, ...) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the string from concatenating the arguments

Output Data Type: With binary inputs, the output data type is binary. With nchar inputs, the output data type is nchar.

Input: all inputs shall be of data type binary or nchar. Can not apply to tag columns.

Notes:

If one of the string inputs is NULL, the resulting output is NULL. The function takes 2 to 8 string values as input. all inputs must be of the same data type. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
CONCAT_WS
```
SELECT CONCAT_WS(separator, str1|column1, str2|column2, ...) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the string from concatenating the arguments with separator.

Output Data Type: With binary inputs, the output data type is binary. With nchar inputs, the output data type is nchar.

Input: all inputs shall be of data type binary or nchar. Can not apply to tag columns.

Notes:

Returns NULL when the separator is NULL. If the separator is not NULL and all the other string values are NULL, the result is an empty string. The function takes 3 to 9 string values as input. all inputs must be of the same data type. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
LENGTH
```
SELECT LENGTH(str|column) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the length of the string measure in bytes

Output Data Type: INT。

Input: BINARY or NCHAR values. Can not apply to tag columns

Notes:

Returns NULL when input is NULL. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
CHAR_LENGTH
```
SELECT CHAR_LENGTH(str|column) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the length of the string measure in characters

Output Data Type: INT。

Input: BINARY or NCHAR values. Can not apply to tag columns

Notes:

Returns NULL when input is NULL. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
LOWER
```
SELECT LOWER(str|column) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the lower case of input value

Output Data Type: BINARY or NCHAR. Same data type as Input.

Input: BINARY or NCHAR values. Can not apply to tag columns

Notes:

Returns NULL when input is NULL. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
UPPER
```
SELECT UPPER(str|column) FROM { tb_name | stb_name } [WHERE clause]
```
Function: Returns the upper case of input value

Output Data Type: BINARY or NCHAR. Same data type as Input.

Input: BINARY or NCHAR values. Can not apply to tag columns

Notes:

Returns NULL when input is NULL. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
LTRIM
```
SELECT LTRIM(str|column) FROM { tb_name | stb_name } [WHERE clause]
```
Function: removes leading spaces from a string

Output Data Type: BINARY or NCHAR. Same data type as Input.

Input: BINARY or NCHAR values. Can not apply to tag columns

Notes:

Returns NULL when input is NULL. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
RTRIM
```
SELECT RTRIM(str|column) FROM { tb_name | stb_name } [WHERE clause]
```
Function: removes trailing spaces from a string

Output Data Type: BINARY or NCHAR. Same data type as Input.

Input: BINARY or NCHAR values. Can not apply to tag columns

Notes:

Returns NULL when input is NULL. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
SUBSTR
```
SELECT SUBSTR(str,pos[,len]) FROM { tb_name | stb_name } [WHERE clause]
```
Function: extracts substring from a string str, starting from pos and extracting len characters.

Output Data Type: BINARY or NCHAR. Same data type as Input.

Input: BINARY or NCHAR values. Can not apply to tag columns

Notes:

Returns NULL when input is NULL. Input pos can be negative or positive. If it is a positive number, the beginning of the substring is pos characters from the beginning of the string. If it is a negative number, the beginning of the substring is pos characters from the end of the string If input len is omitted, the output is whole substring starting from pos. This function applies to normal table, child table and super table This function applies to bother out query and inner query Supported after version 2.6.0.x
Four Operations
```
SELECT field_name [+|-|*|/|%][Value|field_name] FROM { tb_name | stb_name }  [WHERE clause];
```
Function: Calculation results of addition, subtraction, multiplication, division and remainder of values in a column or among multiple columns in statistics/STable.

Returned Data Type: Double.

Applicable Fields: All types except timestamp, binary, nchar, bool.

Note:
1. Calculation between two or more columns is supported, and the calculation priorities can be controlled by parentheses();
2. The NULL field does not participate in the calculation. If a row involved in calculation contains NULL, the calculation result of the row is NULL.

STATECOUNT

SELECT STATECOUNT(field_name, oper, val) FROM { tb_name | stb_name } [WHERE clause];

Function: Returns the number of consecutive records that meet a certain condition, and the result is appended to each row as a new column. The condition is calculated according to the parameters. If the condition is true, it will be increased by 1. If the condition is false, it will be reset to -1. If the data is NULL, the data will be skipped.

Range:

oper : LT(<),GT(>),LE(<=),GE(>=),NE(!=),EQ(=),case insensitive.
val : Number.

Returned Data Type: Integer。

Applicable Fields: All types except timestamp, binary, nchar, bool.

Supported version: Version after 2.6.0 .

Note:

This function can be applied to ordinary tables. When a separate timeline is divided by group by, it is used for super tables (i.e. group by TBNAME).
Cannot be used with window operations，such as interval/state_window/session_window.

Example:

taos> select ts,dbig from statef2;
          ts               |         dbig          |
========================================================
2021-10-15 00:31:33.000000000 |                     1 |
2021-10-17 00:31:31.000000000 |                  NULL |
2021-12-24 00:31:34.000000000 |                     2 |
2022-01-01 08:00:05.000000000 |                    19 |
2022-01-01 08:00:06.000000000 |                  NULL |
2022-01-01 08:00:07.000000000 |                     9 |
Query OK, 6 row(s) in set (0.002977s)

taos> select stateCount(dbig,GT,2) from statef2;
ts               |         dbig          | statecount(dbig,gt,2) |
================================================================================
2021-10-15 00:31:33.000000000 |                     1 |                    -1 |
2021-10-17 00:31:31.000000000 |                  NULL |                  NULL |
2021-12-24 00:31:34.000000000 |                     2 |                    -1 |
2022-01-01 08:00:05.000000000 |                    19 |                     1 |
2022-01-01 08:00:06.000000000 |                  NULL |                  NULL |
2022-01-01 08:00:07.000000000 |                     9 |                     2 |
Query OK, 6 row(s) in set (0.002791s)

STATEDURATION

SELECT stateDuration(field_name, oper, val, unit) FROM { tb_name | stb_name } [WHERE clause];

Function: Returns the length of time of continuous records that meet a certain condition, and the result is appended to each row as a new column. The condition is calculated according to the parameters. If the condition is true, the length of time between two records will be added (the length of time of the first record that meets the condition is recorded as 0). If the condition is false, it will be reset to -1. If the data is NULL, the data will be skipped.

Range：

oper : LT(<),GT(>),LE(<=),GE(>=),NE(!=),EQ(=),case insensitive.
val : Number.
unit : Unit of time length, range [1s, 1M, 1H], less than one unit is rounded off. The default is 1s.

Returned Data Type: Integer。

Applicable Fields: All types except timestamp, binary, nchar, bool.

Supported version: Version after 2.6.0 .

Note:

This function can be applied to ordinary tables. When a separate timeline is divided by group by, it is used for super tables (i.e. group by TBNAME).
Cannot be used with window operations，such as interval/state_window/session_window.

Example:

taos> select ts,dbig from statef2;
          ts               |         dbig          |
========================================================
2021-10-15 00:31:33.000000000 |                     1 |
2021-10-17 00:31:31.000000000 |                  NULL |
2021-12-24 00:31:34.000000000 |                     2 |
2022-01-01 08:00:05.000000000 |                    19 |
2022-01-01 08:00:06.000000000 |                  NULL |
2022-01-01 08:00:07.000000000 |                     9 |
Query OK, 6 row(s) in set (0.002407s)

taos> select stateDuration(dbig,GT,2) from statef2;
ts               |         dbig          | stateduration(dbig,gt,2) |
===================================================================================
2021-10-15 00:31:33.000000000 |                     1 |                       -1 |
2021-10-17 00:31:31.000000000 |                  NULL |                     NULL |
2021-12-24 00:31:34.000000000 |                     2 |                       -1 |
2022-01-01 08:00:05.000000000 |                    19 |                        0 |
2022-01-01 08:00:06.000000000 |                  NULL |                     NULL |
2022-01-01 08:00:07.000000000 |                     9 |                        2 |
Query OK, 6 row(s) in set (0.002613s)

HISTOGRAM

SELECT HISTOGRAM(field_name，bin_type, bin_description, normalized) FROM tb_name [WHERE clause];

Function: Returns count of data points in user-specified ranges.

Return Data Type: Double or INT64, depends on normalized parameter settings.

Applicable Fields: Numerical types.

Applied to: table stable.

Note:

This function is supported since 2.6.0.0.
bin_type: parameter to indicate the bucket type, valid inputs are: "user_input", "linear_bin", "log_bin"。 3）bin_description: parameter to describe how to generate buckets，can be in the following JSON formats for each bin_type respectively:
- "user_input": "[1, 3, 5, 7]" User defined specified bin values.
- "linear_bin": "{"start": 0.0, "width": 5.0, "count": 5, "infinity": true}" "start" - bin starting point. "width" - bin offset. "count" - number of bins generated. "infinity" - whether to add（-inf, inf）as start/end point in generated set of bins. The above "linear_bin" descriptor generates a set of bins: [-inf, 0.0, 5.0, 10.0, 15.0, 20.0, +inf].
- "log_bin": "{"start":1.0, "factor": 2.0, "count": 5, "infinity": true}" "start" - bin starting point. "factor" - exponential factor of bin offset. "count" - number of bins generated. "infinity" - whether to add（-inf, inf）as start/end point in generated range of bins. The above "log_bin" descriptor generates a set of bins:[-inf, 1.0, 2.0, 4.0, 8.0, 16.0, +inf]. 4）normalized: setting to 1/0 to turn on/off result normalization.

Example:

 taos> SELECT HISTOGRAM(voltage, "user_input", "[1,3,5,7]", 1) FROM meters;
     histogram(voltage, "user_input", "[1,3,5,7]", 1) |
 =======================================================
 {"lower_bin":1, "upper_bin":3, "count":0.333333}     |
 {"lower_bin":3, "upper_bin":5, "count":0.333333}     |
 {"lower_bin":5, "upper_bin":7, "count":0.333333}     |
 Query OK, 3 row(s) in set (0.004273s)

 taos> SELECT HISTOGRAM(voltage, 'linear_bin', '{"start": 1, "width": 3, "count": 3, "infinity": false}', 0) FROM meters;
     histogram(voltage, 'linear_bin', '{"start": 1, "width": 3, " |
 ===================================================================
 {"lower_bin":1, "upper_bin":4, "count":3}                        |
 {"lower_bin":4, "upper_bin":7, "count":3}                        |
 {"lower_bin":7, "upper_bin":10, "count":3}                       |
 Query OK, 3 row(s) in set (0.004887s)

 taos> SELECT HISTOGRAM(voltage, 'log_bin', '{"start": 1, "factor": 3, "count": 3, "infinity": true}', 0) FROM meters;
 histogram(voltage, 'log_bin', '{"start": 1, "factor": 3, "count" |
 ===================================================================
 {"lower_bin":-inf, "upper_bin":1, "count":3}                     |
 {"lower_bin":1, "upper_bin":3, "count":2}                        |
 {"lower_bin":3, "upper_bin":9, "count":6}                        |
 {"lower_bin":9, "upper_bin":27, "count":3}                       |
 {"lower_bin":27, "upper_bin":inf, "count":1}                     |

Time Functions

Starting from version 2.6.0.0, TDengine supports following time related functions:

NOW

SELECT NOW() FROM { tb_name | stb_name } [WHERE clause];
SELECT select_expr FROM { tb_name | stb_name } WHERE ts_col cond_operator NOW();
INSERT INTO tb_name VALUES (NOW(), ...);

Function: Returns current time of client.

Returned Data Type: TIMESTAMP type.

Applicable Fields: Can only be applied to TIMESTAMP field when used in WHERE or INSERT clause.

Applied to: table stable.

Note: 1）Support arithmetic operations，e.g. NOW() + 1s. Valid time unit: b(nanosecond)、u(microsecond)、a(millisecond)、s(second)、m(minute)、h(hour)、d(day)、w(week). 2）Returned timestamp precision is consist with current DATABASE precision settings.

Example:

taos> SELECT NOW() FROM meters;
          now()          |
==========================
  2022-02-02 02:02:02.456 |
Query OK, 1 row(s) in set (0.002093s)

taos> SELECT NOW() + 1h FROM meters;
       now() + 1h         |
==========================
  2022-02-02 03:02:02.456 |
Query OK, 1 row(s) in set (0.002093s)

taos> SELECT COUNT(voltage) FROM d1001 WHERE ts < NOW();
        count(voltage)       |
=============================
                           5 |
Query OK, 5 row(s) in set (0.004475s)

taos> INSERT INTO d1001 VALUES (NOW(), 10.2, 219, 0.32);
Query OK, 1 of 1 row(s) in database (0.002210s)

TODAY

SELECT TODAY() FROM { tb_name | stb_name } [WHERE clause];
SELECT select_expr FROM { tb_name | stb_name } WHERE ts_col cond_operator TODAY()];
INSERT INTO tb_name VALUES (TODAY(), ...);

Function: Returns current date of client.

Returned Data Type: TIMESTAMP type。

Applicable Fields: Can only be applied to TIMESTAMP field when used in WHERE or INSERT clause.

Applied to: table stable.

Note: 1）Support arithmetic operations, e.g. TODAY() + 1s. Valid time unit: b(nanosecond)、u(microsecond)、a(millisecond)、s(second)、m(minute)、h(hour)、d(day)、w(week). 2）Returned timestamp precision is consist with current DATABASE precision settings.

Example:

taos> SELECT TODAY() FROM meters;
         today()          |
==========================
  2022-02-02 00:00:00.000 |
Query OK, 1 row(s) in set (0.002093s)

taos> SELECT TODAY() + 1h FROM meters;
      today() + 1h        |
==========================
  2022-02-02 01:00:00.000 |
Query OK, 1 row(s) in set (0.002093s)

taos> SELECT COUNT(voltage) FROM d1001 WHERE ts < TODAY();
        count(voltage)       |
=============================
                           5 |
Query OK, 5 row(s) in set (0.004475s)

taos> INSERT INTO d1001 VALUES (TODAY(), 10.2, 219, 0.32);
Query OK, 1 of 1 row(s) in database (0.002210s)

TIMEZONE

SELECT TIMEZONE() FROM { tb_name | stb_name } [WHERE clause];

Function: Returns current time zone information of client.

Returned Data Type: BINARY type.

Applicable Fields: N/A.

Applied to: table stable.

Example:

taos> SELECT TIMEZONE() FROM meters;
           timezone()           |
=================================
 UTC (UTC, +0000)               |
Query OK, 1 row(s) in set (0.002093s)

TO_ISO8601

SELECT TO_ISO8601(ts_val | ts_col) FROM { tb_name | stb_name } [WHERE clause];

Function: Convert UNIX timestamp to ISO8601 standard date-time format string, with client time zone information attached.

Returned Data Type: BINARY type.

Applicable Fields: UNIX timestamp constant and TIMESTAMP type columns.

Applied to: table stable.

Note: If input is UNIX timestamp constant，returned ISO8601 format precision is determined by input timestamp digits. If input is TIMESTAMP type column, returned ISO8601 format precision is consist with current DATABASE precision settings.

Example:

taos> SELECT TO_ISO8601(1643738400) FROM meters;
   to_iso8601(1643738400)    |
==============================
 2022-02-02T02:00:00+0800    |

taos> SELECT TO_ISO8601(ts) FROM meters;
       to_iso8601(ts)        |
==============================
 2022-02-02T02:00:00+0800    |
 2022-02-02T02:00:00+0800    |
 2022-02-02T02:00:00+0800    |

TO_UNIXTIMESTAMP

SELECT TO_UNIXTIMESTAMP(datetime_string | ts_col) FROM { tb_name | stb_name } [WHERE clause];

Function: Convert date-time format string to UNIX timestamp.

Returned Data Type: INT64.

Applicable Fields: String literal or BINARY/NCHAR type columns.

Applied to: table stable.

Note: 1）Input date-time string format should conform ISO8601/RFC3339 standard，otherwise conversion will fail and 0 is returned. 2）Returned timestamp precision is consist with current DATABASE precision settings.

Example:

taos> SELECT TO_UNIXTIMESTAMP("2022-02-02T02:00:00.000Z") FROM meters;
to_unixtimestamp("2022-02-02T02:00:00.000Z") |
==============================================
                               1643767200000 |

taos> SELECT TO_UNIXTIMESTAMP(col_binary) FROM meters;
      to_unixtimestamp(col_binary)     |
========================================
                         1643767200000 |
                         1643767200000 |
                         1643767200000 |

TIMETRUNCATE

SELECT TIMETRUNCATE(ts_val | datetime_string | ts_col, time_unit) FROM { tb_name | stb_name } [WHERE clause];

Function: Truncate timestamp by time_unit.

Returned Data Type: TIMESTAMP type.

Applicable Fields: UNIX timestamp, date-time format string, and TIMESTAMP type columns.

Applied to: table stable.

Note: 1）Supported time_unit: 1u(microsecond)，1a(millisecond)，1s(second)，1m(minute)，1h(hour)，1d(day)。 2）Returned timestamp precision is consist with current DATABASE precision settings.

Example:

taos> SELECT TIMETRUNCATE(1643738522000, 1h) FROM meters;
  timetruncate(1643738522000, 1h) |
===================================
      2022-02-02 02:00:00.000     |
Query OK, 1 row(s) in set (0.001499s)

taos> SELECT TIMETRUNCATE("2022-02-02 02:02:02", 1h) FROM meters;
  timetruncate("2022-02-02 02:02:02", 1h) |
===========================================
      2022-02-02 02:00:00.000             |
Query OK, 1 row(s) in set (0.003903s)

taos> SELECT TIMETRUNCATE(ts, 1h) FROM meters;
  timetruncate(ts, 1h)   |
==========================
 2022-02-02 02:00:00.000 |
 2022-02-02 02:00:00.000 |
 2022-02-02 02:00:00.000 |
Query OK, 3 row(s) in set (0.003903s)

TIMEDIFF

SELECT TIMEDIFF(ts_val1 | datetime_string1 | ts_col1, ts_val2 | datetime_string2 | ts_col2 [, time_unit]) FROM { tb_name | stb_name } [WHERE clause];

Function: Calculate duration between two timestamps with time_unit precision。

Returned Data Type: INT64.

Applicable Fields: UNIX timestamp, date-time format string, and TIMESTAMP type columns.

Applied to: table stable.

Note: 1）Supported time_unit: 1u(microsecond)，1a(millisecond)，1s(second)，1m(minute)，1h(hour)，1d(day)。 2）If time_unit is unspecified, returned time duration unit is consist with current DATABASE precision settings.

Example:

taos> SELECT TIMEDIFF(1643738400000, 1643742000000) FROM meters;
 timediff(1643738400000, 1643742000000) |
=========================================
                                3600000 |
Query OK, 1 row(s) in set (0.002553s)
taos> SELECT TIMEDIFF(1643738400000, 1643742000000, 1h) FROM meters;
 timediff(1643738400000, 1643742000000, 1h) |
=============================================
                                          1 |
Query OK, 1 row(s) in set (0.003726s)

taos> SELECT TIMEDIFF("2022-02-02 03:00:00", "2022-02-02 02:00:00", 1h) FROM meters;
 timediff("2022-02-02 03:00:00", "2022-02-02 02:00:00", 1h) |
=============================================================
                                                          1 |
Query OK, 1 row(s) in set (0.001937s)

taos> SELECT TIMEDIFF(ts_col1, ts_col2, 1h) FROM meters;
   timediff(ts_col1, ts_col2, 1h) |
===================================
                                1 |
Query OK, 1 row(s) in set (0.001937s)

Time-dimension Aggregation

TDengine supports aggregating by intervals (time range). Data in a table can partitioned by intervals and aggregated to generate results. For example, a temperature sensor collects data once per second, but the average temperature needs to be queried every 10 minutes. This aggregation is suitable for down sample operation, and the syntax is as follows:

SELECT function_list FROM tb_name
  [WHERE where_condition]
  INTERVAL (interval [, offset])
  [SLIDING sliding]
  [FILL ({NONE | VALUE | PREV | NULL | LINEAR | NEXT})]

SELECT function_list FROM stb_name
  [WHERE where_condition]
  INTERVAL (interval [, offset])
  [SLIDING sliding]
  [FILL ({ VALUE | PREV | NULL | LINEAR | NEXT})]
  [GROUP BY tags]

The length of aggregation interval is specified by keyword INTERVAL, the min time interval is 10 milliseconds (10a), and offset is supported (the offset must be less than interval). In aggregation queries, the aggregator and selector functions that can be executed simultaneously are limited to functions with one single output: count, avg, sum, stddev, leastsquares, percentile, min, max, first, last. Functions with multiple rows of output results (such as top, bottom, diff, and four operations) cannot be used.
WHERE statement specifies the start and end time of a query and other filters
FILL statement specifies a filling mode when data missed in a certain interval. Applicable filling modes include the following:
1. Do not fill: NONE (default filing mode).
2. VALUE filling: Fixed value filling, where the filled value needs to be specified. For example: fill (VALUE, 1.23).
3. NULL filling: Fill the data with NULL. For example: fill (NULL).
4. PREV filling: Filling data with the previous non-NULL value. For example: fill (PREV).
5. NEXT filling: Filling data with the next non-NULL value. For example: fill (NEXT).

Note:

When using a FILL statement, a large number of filling outputs may be generated. Be sure to specify the time interval for the query. For each query, system can return no more than 10 million results with interpolation.
In a time-dimension aggregation, the time-series in returned results increases strictly monotonously.
If the query object is a STable, the aggregator function will act on the data of all tables under the STable that meet the value filters. If group by statement is not used in the query, the returned result increases strictly monotonously according to time-series; If group by statement is used to group in the query, each group in the returned result does not increase strictly monotonously according to time-series.

Example: The statement for building a database for smart meter is as follows:

CREATE TABLE meters (ts TIMESTAMP, current FLOAT, voltage INT, phase FLOAT) TAGS (location BINARY(64), groupId INT);

According to the data collected by the smart meter, the average value, maximum value, median current of current data in the past 24 hours are calculated in a phase of 10 minutes, and the current trend with time changes is fitted to a straight line. If there is no calculated value, fill it with the previous non-NULL value. The query statement used is as follows:

SELECT AVG(current), MAX(current), LEASTSQUARES(current, start_val, step_val), PERCENTILE(current, 50) FROM meters
  WHERE ts>=NOW-1d
  INTERVAL(10m)
  FILL(PREV);

TAOS SQL Boundary Restrictions

Max database name length is 32
Max length of table name is 192, and max length of each data row is 48K (it's 16K prior to 2.1.7.0) characters
Max length of column name is 64, max number of columns allowed is 1024, and min number of columns allowed is 2. The first column must be a timestamp
Max number of tags allowed is 128, down to 1, and total length of tags does not exceed 16K characters
Max length of SQL statement is 65480 characters, but it can be modified by system configuration parameter maxSQLLength, and max length can be configured to 1M
Number of databases, STables and tables are not limited by system, but only limited by system resources

Other TAOS SQL Conventions

Restrictions on group by

TAOS SQL supports group by operation on tags, tbnames and ordinary columns, required that only one column and which has less than 100,000 unique values.

Restrictions on join operation

TAOS SQL supports join columns of two tables by Primary Key timestamp between them, and does not support four arithmetic operations after tables aggregated for the time being.

Availability of is no null

Is not null supports all types of columns. Non-null expression is < > "" and only applies to columns of non-numeric types.

Restrictions on order by

A non super table can only have one order by.
The super table can have at most two order by expression, and the second must be ts.
Order by tag must be the same tag as group by tag. TBNAME is as logical as tag.
Order by ordinary column must be the same ordinary column as group by or top/bottom. If both group by and top / bottom exist, order by must be in the same column as group by.
There are both order by and group by. The internal of the group is sorted by ts
Order by ts.

JSON type instructions

Syntax description

Create JSON type tag

create stable s1 (ts timestamp, v1 int) tags (info json)

create table s1_1 using s1 tags ('{"k1": "v1"}')

JSON value operator(->)

select * from s1 where info->'k1' = 'v1'

select info->'k1' from s1

JSON key existence operator(contains)

select * from s1 where info contains 'k2'

select * from s1 where info contains 'k1'

Supported operations
1. In where condition，support match/nmatch/between and/like/and/or/is null/is no null，in operator is not support.
```
select * from s1 where info→'k1' match 'v*'; 

select * from s1 where info→'k1' like 'v%' and info contains 'k2';

select * from s1 where info is null; 

select * from s1 where info->'k1' is not null
```
2. JSON tag is supported in group by、order by、join clause、union all and subquery，like group by json->'key'
3. Support distinct operator.
```
select distinct info→'k1' from s1
```
4. Tag
  
  Support change JSON tag（full coverage）
  
  Support change the name of JSON tag
  
  Not support add JSON tag, delete JSON tag
Other constraints
1. Only tag columns can use JSON type. If JSON tag is used, there can only be one tag column.
2. Length limit:The length of the key in JSON cannot exceed 256, and the key must be printable ASCII characters; The total length of JSON string does not exceed 4096 bytes.
3. JSON format restrictions:
4. JSON input string can be empty (""," ","\t" or null) or object, and cannot be nonempty string, boolean or array.
5. Object can be {}, if the object is {}, the whole JSON string is marked as empty. The key can be "", if the key is "", the K-V pair will be ignored in the JSON string.
6. Value can be a number (int/double) or string, bool or null, not an array. Nesting is not allowed.
7. If two identical keys appear in the JSON string, the first one will take effect.
8. Escape is not supported in JSON string.
9. Null is returned when querying the key that does not exist in JSON.
10. When JSON tag is used as the sub query result, parsing and querying the JSON string in the sub query is no longer supported in the upper level query.
  
  The following query is not supported:
```
select jtag→'key' from (select jtag from stable)

select jtag->'key' from (select jtag from stable) where jtag->'key'>0
```
  Escape character description

Special Character Escape Sequences (since version 2.4.0.4)

Escape Sequence	Character Represented by Sequence
`\'`	A single quote (') character
`\"`	A double quote (") character
\n	A newline (linefeed) character
\r	A carriage return character
\t	A tab character
`\\`	A backslash () character
`\%`	A % character; see note following the table
`\_`	A _ character; see note following the table

Escape character usage rules
- The escape characters that in a identifier (database name, table name, column name)
  1. Normal identifier： The wrong identifier is prompted directly, because the identifier must be numbers, letters and underscores, and cannot start with a number.
  2. Backquote`` identifier： Keep it as it is.
- The escape characters that in a data
  1. The escape character defined above will be escaped (% and _ see the description below). If there is no matching escape character, the escape character will be ignored.
  2. The \% and \_ sequences are used to search for literal instances of % and in pattern-matching contexts where they would otherwise be interpreted as wildcard characters.If you use \% or \_ outside of pattern-matching contexts, they evaluate to the strings \% and \_, not to % and .

支持和反馈

感谢您成为我们社区的一员！欢迎您对本文档或其他任何 TDengine 错误进行修改或报告。

反馈问题 | 获取专业服务

TAOS SQL

Taos-sql

TAOS SQL

Data Types

Database Management

Table Management

STable Management

TAG Management in STable

Data Writing

Data Query

Query Syntax:

SELECT Clause

Wildcard character

Tag Column

Obtain the de-duplicated value of a tag column

Column name in result set

Implicit result column

List of STable

Special Functions

Special keywords in TAOS SQL

Tips

Supported Filtering Operations

SQL Example

SQL Functions

Selector Functions

Computing Functions

Time Functions

Time-dimension Aggregation

TAOS SQL Boundary Restrictions

Other TAOS SQL Conventions

JSON type instructions

Escape character description

支持和反馈