Update docs.md
This commit is contained in:
parent
df16603548
commit
6270734545
|
@ -37,7 +37,7 @@ With TDengine, the most important thing is timestamp. When creating and insertin
|
|||
- Epch 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 resolution by default. Microsecond/nanosecond resolutions can be set using CREATE DATABASE with PRECISION parameter.(Nanosecond resolution is supported from version 2.1.5.0 onwards)
|
||||
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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue