TQL has four primitive types: string, number, boolean and time.
string
Define constant strings with quotation marks, as in traditional programming languages: single (’), double (") and backtick. Braces can also enclose a string.
A backtick string is useful when you need to define a string in multiple lines that includes quotation marks, such as a long SQL statement.
When multi-line content contains another backtick or brace characters ({, }), use tagged raw literals to avoid boundary conflicts.
Tagged backtick: `<<TAG ... TAG`
Tagged brace block: {<<TAG ... TAG}
Both forms treat the body as raw text and close at the tagged closing line.
Example) Escaping single quote with backslash(\')
1
2
SQL('select * from example where name=\'temperature\' limit 10')CSV()
Example) Double quote string
1
2
SQL("select * from example where name='temperature' limit 10")CSV()
Example) Use multi-lines sql statement without escaping by backtick(`)
1
2
3
4
5
SQL(`select *
from example
where name='temperature'
limit 10`)CSV()
1
2
3
4
5
SCRIPT(`<<JS
// this is a function return '{'
function a () { return '{' }
JS`)CSV()
1
2
3
4
5
6
MARKDOWN({<<MD```mermaid
erDiagram
CUSTOMER ||--o{ ORDER :places
```MD})
There is a convenient way to specify a JSON string in a TQL script by using double braces ({{ }}).
It doesn’t require escaping quotation marks.
The two string expressions used below are equivalent.
Time type values can be created by calling time(), parseTime() functions, or retrieved from a DATETIME column of a SQL query result.
timeZone
TimeZone type values can be created by calling tz() function.
ex) tz('UTC'), tz('Local'), tz('Asia/Seoul')
list
A list is an array of other values, it can be created by calling list() function.
ex) list(1, 2, 3)
dictionary
A dictionary is a set of (string) name and value pairs, created by calling dict() function.
ex) dict("name", "pi", "value", 3.14)
Statements
Every statement in TQL should be a function call except the literal constants of string, number and boolean.
// A comment line starts with '//'
SQL_SELECT('time','value',from('example','temperature'),limit(10))CSV()
SRC and SINK
Every .tql script should start with one source (SRC) statement which generates a record or records.
For example, SQL(), SQL_SELECT() and SCRIPT() that generates records with $.yield(), $.yieldKey() can be a source.
And the last statement should be a sink (SINK) statement that encodes the result or writes it into the database.
For example, CSV(), JSON(), INSERT(), APPEND() and all CHART() functions can be a sink.
MAP functions
There may be zero or more map functions between source and sink statements.
The names of all map functions are in capital letters; in contrast, lower case camel notation functions are used as arguments of the other map functions.
When external applications call a .tql script via HTTP, they can provide arguments as query parameters.
The function param() retrieves the values of the query parameters in a TQL script.
If the script below is saved as hello2.tql, applications can call it by HTTP GET method with http://127.0.0.1:5654/db/tql/hello2.tql?name=temperature&count=10.
Then param('name') returns "temperature" and param('count') returns the string "10".
The ternary operator ? : is similar to the if-else statement in other programming languages,
as it selects a value by the same logic as an if-else statement.
The ?? operator takes a left and a right operand. If the left operand is defined, it returns its value; otherwise it returns the right operand.
The example below shows the common use case of the ?? operator. If the caller did not provide query parameters, the right operand is taken as the default value.
The //+ name=value directive provides instructions on how Machbase Neo should execute the TQL script.
log-level
Since v8.0.47
Set the log-level to one of [TRACE | DEBUG | INFO | WARN | ERROR].
The default is ERROR, which suppresses most log messages when called from HTTP and MQTT APIs.
1
2
3
4
//+ log-level=TRACE
SQL(`select * from my_table where name = ?`,param("name"))WHEN(true,doLog('hello world'))CSV()
sql-thread-lock
Since v8.0.47
This pragma ensures that the specified SQL() runs on a dedicated native thread,
which is terminated once the TQL script completes.
It works only with the SRC SQL().
According to internal performance tests with a hundred simultaneous HTTP client requests to execute the TQL file,
enabling this option increases response latency by 35% but significantly reduces memory release delay.
1
2
3
4
//+ sql-thread-lock
SQL(`select * from my_table where name = ?`,param("name"))WHEN(true,doLog('hello world'))CSV()