Date and time functions
This page describes the available functions to assist with performing time-based calculations.
info
Checking if tables contain a designated timestamp column can be done via the
tables()
and table_columns()
functions which are described in the
meta functions documentation page.
#
systimestampsystimestamp()
- offset from UTC Epoch in microseconds. Calculates
UTC timestamp
using system's real time clock. The value is affected by
discontinuous jumps in the system time (e.g., if the system administrator
manually changes the system time).
Arguments:
systimestamp()
does not accept arguments.
Return value:
Return value type is timestamp
.
Examples:
ts | reading |
---|---|
2020-01-02T19:28:48.727516Z | 123.5 |
#
sysdatesysdate()
- returns the timestamp of the host system as a date
with
millisecond
precision.
Calculates UTC date
with millisecond precision using system's real time clock.
The value is affected by discontinuous jumps in the system time (e.g., if the
system administrator manually changes the system time).
Arguments:
sysdate()
does not accept arguments.
Return value:
Return value type is date
.
Examples:
sysdate | reading |
---|---|
2020-01-02T19:28:48.727516Z | 123.5 |
#
nownow()
- offset from UTC Epoch in microseconds.
Calculates UTC timestamp
using system's real time clock. Unlike
sysdatetime()
, it does not change within the query execution timeframe and
should be used in WHERE clause to filter designated timestamp column relative to
current time, i.e.:
SELECT now() FROM long_sequence(200)
will return the same timestamp for all rowsSELECT systimestamp() FROM long_sequence(200)
will have new timestamp values for each row
Arguments:
now()
does not accept arguments.
Return value:
Return value type is timestamp
.
Examples:
created | origin |
---|---|
2021-02-01T21:51:34.443726Z | 1 |
now |
---|
2021-02-01T21:51:34.443726Z |
2021-02-01T21:51:34.443726Z |
2021-02-01T21:51:34.443726Z |
#
timestamp_ceiltimestamp_ceil(unit, timestamp)
- performs a ceiling calculation on a
timestamp by given unit.
A unit must be provided to specify which granularity to perform rounding.
Arguments:
timestamp_ceil(unit, timestamp)
has the following arguments:
unit
- may be one of the following:
T
millisecondss
secondsm
minutesh
hoursd
daysM
monthsy
year
timestamp
- any timestamp value
Return value:
Return value type is timestamp
.
Examples:
ts | c_milli | c_second | c_minute | c_hour | c_day | c_month | c_year |
---|---|---|---|---|---|---|---|
2016-02-10T16:18:22.862145Z | 2016-02-10T16:18:22.863000Z | 2016-02-10T16:18:23.000000Z | 2016-02-10T16:19:00.000000Z | 2016-02-10T17:00:00.000000Z | 2016-02-11T00:00:00.000000Z | 2016-03-01T00:00:00.000000Z | 2017-01-01T00:00:00.000000Z" |
#
timestamp_floortimestamp_floor(unit, timestamp)
- performs a floor calculation on a timestamp
by given unit.
A unit must be provided to specify which granularity to perform rounding.
Arguments:
timestamp_floor(unit, timestamp)
has the following arguments:
unit
- may be one of the following:
T
millisecondss
secondsm
minutesh
hoursd
daysM
monthsy
year
timestamp
- any timestamp value
Return value:
Return value type is timestamp
.
Examples:
ts | f_milli | f_second | f_minute | f_hour | f_day | f_month | f_year |
---|---|---|---|---|---|---|---|
2016-02-10T16:18:22.862145Z | 2016-02-10T16:18:22.862000Z | 2016-02-10T16:18:22.000000Z | 2016-02-10T16:18:00.000000Z | 2016-02-10T16:00:00.000000Z | 2016-02-10T00:00:00.000000Z | 2016-02-01T00:00:00.000000Z | 2016-01-01T00:00:00.000000Z |
#
to_timestampto_timestamp(string, format)
- converts string
to timestamp
by using the
supplied format
to extract the value with microsecond precision.
When the format
definition does not match the string
input, the result will
be null
.
For more information about recognized timestamp formats, see the date and timestamp format section.
Arguments:
string
is any string that represents a date and/or time.format
is a string that describes the timestamp format in whichstring
is expressed.
Return value:
Return value type is timestamp
. QuestDB provides timestamp
with microsecond
resolution. Input strings with nanosecond precision will be parsed but lose the
precision.
Examples:
to_timestamp |
---|
2020-03-01T15:43:21.127329Z |
to_timestamp |
---|
2020-03-01T15:43:00.000000Z |
to_timestamp |
---|
null |
timestamp | value |
---|---|
2019-12-12T12:15:00.000000Z | 123.5 |
Note that conversion of ISO timestamp format is optional. QuestDB automatically
converts string
to timestamp
if it is a partial or full form of
yyyy-MM-ddTHH:mm:ss.SSSUUU
or yyyy-MM-dd HH:mm:ss.SSSUUU
with a valid time
offset, +01:00
or Z
. See more examples in
Native timestamp
format](/docs/reference/sql/where#native-timestamp-format).
#
to_dateto_date(string, format)
- converts string to date
by using the supplied
format
to extract the value.
Will convert a string
to date
using the format definition passed as an
argument. When the format
definition does not match the string
input, the
result will be null
.
For more information about recognized timestamp formats, see the date and timestamp format section.
Arguments:
string
is any string that represents a date and/or time.format
is a string that describes thedate format
in whichstring
is expressed.
Return value:
Return value type is date
Examples:
to_date |
---|
2020-03-01T15:43:21.000Z |
to_date |
---|
null |
date | value |
---|---|
2019-12-12T12:15:00.000Z | 123.5 |
#
to_strto_str(value, format)
- converts date or timestamp value to a string in the
specified format
Will convert a date or timestamp value to a string using the format definition
passed as an argument. When elements in the format
definition are
unrecognized, they will be passed-through as string.
For more information about recognized timestamp formats, see the date and timestamp format section.
Arguments:
value
is anydate
ortimestamp
format
is a timestamp format.
Return value:
Return value type is string
Examples:
- Basic example
to_str |
---|
2020-03-04 |
- With unrecognized timestamp definition
to_str |
---|
2020-03-04 gooD DAY 123 |
#
to_timezoneto_timezone(timestamp, timezone)
- converts a timestamp value to a specified
timezone. For more information on the time zone database used for this function,
see the
QuestDB time zone database documentation.
Arguments:
timestamp
is anytimestamp
as Unix timestamp or string equivalenttimezone
may beCountry/City
tz database name, time zone abbreviation such asPST
or in UTC offset in string format.
Return value:
Return value type is timestamp
Examples:
- Unix UTC timestamp in microseconds to
Europe/Berlin
to_timezone |
---|
2021-06-08T17:45:45.000000Z |
- Unix UTC timestamp in microseconds to PST by UTC offset
to_timezone |
---|
2021-06-08T07:45:45.000000Z |
- Timestamp as string to
PST
to_timezone |
---|
2021-06-08T06:45:45.000000Z |
#
to_utcto_utc(timestamp, timezone)
- converts a timestamp by specified timezone to
UTC. May be provided a timezone in string format or a UTC offset in hours and
minutes. For more information on the time zone database used for this function,
see the
QuestDB time zone database documentation.
Arguments:
timestamp
is anytimestamp
as Unix timestamp or string equivalenttimezone
may beCountry/City
tz database name, time zone abbreviation such asPST
or in UTC offset in string format.
Return value:
Return value type is timestamp
Examples:
- Convert a Unix timestamp in microseconds from the
Europe/Berlin
timezone to UTC
to_utc |
---|
2021-06-08T13:45:45.000000Z |
- Unix timestamp in microseconds from PST to UTC by UTC offset
to_utc |
---|
2021-06-08T23:45:45.000000Z |
- Timestamp as string in
PST
to UTC
to_utc |
---|
2021-06-08T20:45:45.000000Z |
#
dateadddateadd(period, n, startDate)
- adds n
period
to startDate
.
Arguments:
period
is a char. Period to be added. Available periods ares
,m
,h
,d
,M
,y
.n
is an int. Number of periods to add.startDate
is a timestamp or date. Timestamp to add the periods to.
Return value:
Return value type is timestamp
Examples:
systimestamp | dateadd |
---|---|
2020-04-17T00:30:51.380499Z | 2020-04-17T02:30:51.380499Z |
systimestamp | dateadd |
---|---|
2020-04-17T00:30:51.380499Z | 2020-04-19T00:30:51.380499Z |
systimestamp | dateadd |
---|---|
2020-04-17T00:30:51.380499Z | 2020-06-17T00:30:51.380499Z |
#
datediffdatediff(period, date1, date2)
- returns the absolute number of period
between date1
and date2
.
Arguments:
period
is a char. Period to be added. Available periods ares
,m
,h
,d
,M
,y
.date1
anddate2
are date or timestamp. Dates to compare
Return value:
Return value type is int
Examples:
datediff |
---|
4 |
datediff |
---|
1 |
#
millismillis(value)
- returns the millis
of the second for a given date or
timestamp from 0
to 999
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
millis |
---|
123 |
millis |
---|
123 |
second | count |
---|---|
0 | 2323 |
1 | 6548 |
... | ... |
998 | 9876 |
999 | 2567 |
#
microsmicros(value)
- returns the micros
of the millisecond for a given date or
timestamp from 0
to 999
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
millis |
---|
456 |
millis |
---|
456 |
second | count |
---|---|
0 | 2323 |
1 | 6548 |
... | ... |
998 | 9876 |
999 | 2567 |
#
secondsecond(value)
- returns the second
of the minute for a given date or
timestamp from 0
to 59
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
second |
---|
43 |
second | count |
---|---|
0 | 2323 |
1 | 6548 |
... | ... |
58 | 9876 |
59 | 2567 |
#
minuteminute(value)
- returns the minute
of the hour for a given date or timestamp
from 0
to 59
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
minute |
---|
43 |
minute | count |
---|---|
0 | 2323 |
1 | 6548 |
... | ... |
58 | 9876 |
59 | 2567 |
#
hourhour(value)
- returns the hour
of day for a given date or timestamp from 0
to 23
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
hour |
---|
12 |
hour | count |
---|---|
0 | 2323 |
1 | 6548 |
... | ... |
22 | 9876 |
23 | 2567 |
#
dayday(value)
- returns the day
of month for a given date or timestamp from 1
to 31
.
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
day |
---|
01 |
day | count |
---|---|
1 | 2323 |
2 | 6548 |
... | ... |
30 | 9876 |
31 | 2567 |
#
monthmonth(value)
- returns the month
of year for a given date or timestamp from
1
to 12
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
month |
---|
03 |
month | count |
---|---|
1 | 2323 |
2 | 6548 |
... | ... |
11 | 9876 |
12 | 2567 |
#
yearyear(value)
- returns the year
for a given date or timestamp
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
year |
---|
2020 |
year | count |
---|---|
2015 | 2323 |
2016 | 9876 |
2017 | 2567 |
#
is_leap_yearis_leap_year(value)
- returns true
if the year
of value
is a leap year,
false
otherwise.
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is boolean
Examples:
year | is_leap_year |
---|---|
2020 | true |
2021 | false |
2022 | false |
2023 | false |
2024 | true |
2025 | false |
#
days_in_monthdays_in_month(value)
- returns the number of days in a month from a provided
timestamp or date.
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
month | days_in_month |
---|---|
4 | 30 |
5 | 31 |
6 | 30 |
7 | 31 |
8 | 31 |
#
day_of_weekday_of_week(value)
- returns the day number in a week from 1
(Monday) to 7
(Sunday)
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
day | day_of_week |
---|---|
Monday | 1 |
Tuesday | 2 |
Wednesday | 3 |
Thursday | 4 |
Friday | 5 |
Saturday | 6 |
Sunday | 7 |
#
day_of_week_sunday_firstday_of_week_sunday_first(value)
- returns the day number in a week from 1
(Sunday) to 7
(Saturday)
Arguments:
value
is anytimestamp
ordate
Return value:
Return value type is int
Examples:
day | day_of_week_sunday_first |
---|---|
Monday | 2 |
Tuesday | 3 |
Wednesday | 4 |
Thursday | 5 |
Friday | 6 |
Saturday | 7 |
Sunday | 1 |
#
Date and timestamp formatThe date and timestamp format is formed by units and arbitrary text. A unit is a combination of letters representing a date or time component, as defined by the table below. The letters used to form a unit are case-sensitive.
See Timestamps in QuestDB for more examples of how the units are used to parse inputs.
Unit | Date or Time Component | Presentation | Examples |
---|---|---|---|
G | Era designator | Text | AD |
y | y single digit or greedy year, depending on the input digit number | Year | 1996; 96; 999; 3 |
yy | Two digit year of the current century | Year | 96 (interpreted as 2096) |
yyy | Three-digit year | Year | 999 |
yyyy | Four-digit year | Year | 1996 |
M | Month in year | Month | July; Jul; 07 |
w | Week in year | Number | 27 |
ww | ISO week of year | Number | 2 |
D | Day in year | Number | 189 |
d | Day in month | Number | 10 |
F | Day of week in month | Number | 2 |
E | Day name in week | Text | Tuesday; Tue |
u | Day number of week (1 = Monday, ..., 7 = Sunday) | Number | 1 |
a | Am/pm marker | Text | PM |
H | Hour in day (0-23) | Number | 0 |
k | Hour in day (1-24) | Number | 24 |
K | Hour in am/pm (0-11) | Number | 0 |
h | Hour in am/pm (1-12) | Number | 12 |
m | Minute in hour | Number | 30 |
s | Second in minute | Number | 55 |
SSS | 3-digit millisecond | Number | 978 |
S | Millisecond up to 3 digits: S parses 1 digit when followed by another unit . Otherwise, it parses 3 digits. | Number | 900 |
z | Time zone | General time zone | Pacific Standard Time; PST; GMT-08:00 |
Z | Time zone | RFC 822 time zone | -0800 |
X | Time zone | ISO 8601 time zone | -08; -0800; -08:00 |
UUU | 3-digit microsecond | Number | 698 |
U | Microsecond up to 3 digits: U parses 1 digit when followed by another unit . Otherwise, it parses 3 digits. | Number | 600 |
U+ | 6-digit microsecond | Number | 600 |
N | Nanosecond. QuestDB provides microsecond resolution so the parsed nanosecond will be truncated. | Number | N/A (truncated) |
N+ | 9-digit nanosecond. QuestDB provides microsecond resolution so the parsed nanosecond will be truncated. | Number | N/A (truncated) |
y
#
Examples for greedy year format The interpretation of y
depends on the input digit number:
- If the input year is a two-digit number, the output timestamp assumes the current century.
- Otherwise, the number is interpreted as it is.
Input year | Timestamp value interpreted by y-M | Notes |
---|---|---|
5-03 | 0005-03-01T00:00:00.000000Z | Greedily parsing the number as it is |
05-03 | 2005-03-01T00:00:00.000000Z | Greedily parsing the number assuming current century |
005-03 | 0005-03-01T00:00:00.000000Z | Greedily parsing the number as it is |
0005-03 | 0005-03-01T00:00:00.000000Z | Greedily parsing the number as it is |