Time And Date

The {{< product-name >}} SQL implementation supports time and date functions that are useful when working with time series data.

• current_date
• current_time
• current_timestamp
• date_bin
• date_bin_gapfill
• date_bin_wallclock
• date_bin_wallclock_gapfill
• date_trunc
• datetrunc
• date_format
• date_part
• datepart
• extract
• from_unixtime
• make_date
• now
• today
• to_char
• to_date
• to_local_time
• to_timestamp
• to_timestamp_micros
• to_timestamp_millis
• to_timestamp_nanos
• to_timestamp_seconds
• to_unixtime
• tz

current_date

Returns the current UTC date.

[!Note] current_date returns a DATE32 Arrow type, which isn't supported by InfluxDB. To use with InfluxDB, cast the return value to a timestamp or string.

The current_date() return value is determined at query time and returns the same date, no matter when in the query plan the function executes.

current_date()

{{< expand-wrapper >}} {{% expand "View current_date query example" %}}

The following example uses the sample data set provided in Get started with InfluxDB tutorial.

SELECT
  time,
  temp,
  current_date()::TIMESTAMP AS current_date
FROM home
WHERE
  time > current_date()::TIMESTAMP - INTERVAL '5 years'
LIMIT 3

{{% influxdb/custom-timestamps %}}

{{% /influxdb/custom-timestamps %}}

{{% /expand %}} {{< /expand-wrapper >}}

current_time

Returns the current UTC time.

The current_time() return value is determined at query time and returns the same time, no matter when in the query plan the function executes.

current_time()

{{< expand-wrapper >}} {{% expand "View current_time query example" %}}

The following example uses the sample data set provided in the Get started with InfluxDB tutorial.

SELECT
  time,
  temp,
  current_time() AS current_time
FROM home
LIMIT 3

{{% /expand %}} {{< /expand-wrapper >}}

current_timestamp

Alias of now.

date_bin

Calculates time intervals and returns the start of the interval nearest to the specified timestamp. Use date_bin to downsample time series data by grouping rows into time-based "bins" or "windows" and applying an aggregate or selector function to each window.

For example, if you "bin" or "window" data into 15-minute intervals, an input timestamp of 2023-01-01T18:18:18Z will be updated to the start time of the 15-minute bin it is in: 2023-01-01T18:15:00Z.

date_bin(interval, expression[, origin_timestamp])

Arguments

• interval: Bin interval. Supports the following interval units:

  • nanoseconds
  • microseconds
  • milliseconds
  • seconds
  • minutes
  • hours
  • days
  • weeks
  • months
  • years
  • century

• expression: Time expression to operate on. Can be a constant, column, or function.

• origin_timestamp: Starting point used to determine bin boundaries. Default is the Unix epoch.

{{< expand-wrapper >}} {{% expand "View date_bin query example" %}}

The following query returns the daily average of water levels in the queried time range.

SELECT
  date_bin(INTERVAL '1 day', time, TIMESTAMP '1970-01-01 00:00:00Z') AS time,
  avg("water_level") AS water_level_avg
FROM "h2o_feet"
WHERE
  time >= timestamp '2019-09-10T00:00:00Z'
  AND time <= timestamp '2019-09-20T00:00:00Z'
GROUP BY 1
ORDER BY time DESC

{{% /expand %}} {{< /expand-wrapper >}}

date_bin_gapfill

Calculates time intervals and returns the start of the interval nearest to the specified timestamp. If no rows exist in a time interval, a new row is inserted with a time value set to the interval start time, all columns in the GROUP BY clause populated, and null values in aggregate columns.

Use date_bin_gapfill with interpolate or locf to fill gaps in data at specified time intervals.

date_bin_gapfill(interval, expression[, origin_timestamp])

[!Note] date_bin_gapfill requires time bounds in the WHERE clause.

Arguments

• interval: Bin interval. Supports the following interval units:

  • nanoseconds
  • microseconds
  • milliseconds
  • seconds
  • minutes
  • hours
  • days
  • weeks

The following intervals are not currently supported:

• months

• years

• century

• expression: Time expression to operate on. Can be a constant, column, or function.

• origin_timestamp: Starting point used to determine bin boundaries. Default is the Unix epoch.

Related functions

interpolate, locf

{{< expand-wrapper >}} {{% expand "Use date_bin_gapfill to insert rows when no rows exists" %}}

The following example uses the sample data set provided in the Get started with InfluxDB tutorial.

{{% influxdb/custom-timestamps %}}

SELECT
  date_bin_gapfill(INTERVAL '30 minutes', time) as _time,
  room,
  avg(temp) as temp
FROM home
WHERE
    time >= '2022-01-01T08:00:00Z'
    AND time <= '2022-01-01T10:00:00Z'
GROUP BY _time, room

{{% /influxdb/custom-timestamps %}} {{% /expand %}}

{{% expand "Use date_bin_gapfill to fill gaps in data" %}}

Use interpolate and locf to fill the null values in rows inserted by date_bin_gapfill.

The following examples use the sample data set provided in the Get started with InfluxDB tutorial.

{{< tabs-wrapper >}} {{% tabs "small" %}} interpolate locf {{% /tabs %}} {{% tab-content %}}

The example below uses interpolate to fill null values by interpolating values between non-null values.

{{% influxdb/custom-timestamps %}}

SELECT
  date_bin_gapfill(INTERVAL '30 minutes', time) as _time,
  room,
  interpolate(avg(temp))
FROM home
WHERE
    time >= '2022-01-01T08:00:00Z'
    AND time <= '2022-01-01T10:00:00Z'
GROUP BY _time, room

{{% /influxdb/custom-timestamps %}}

{{% /tab-content %}} {{% tab-content %}}

The example below uses locf to fill null values by carrying the last observed value forward.

{{% influxdb/custom-timestamps %}}

SELECT
  date_bin_gapfill(INTERVAL '30 minutes', time) as _time,
  room,
  locf(avg(temp))
FROM home
WHERE
    time >= '2022-01-01T08:00:00Z'
    AND time <= '2022-01-01T10:00:00Z'
GROUP BY _time, room

{{% /influxdb/custom-timestamps %}}

{{% /tab-content %}} {{< /tabs-wrapper >}}

{{% /expand %}} {{< /expand-wrapper >}}

date_bin_wallclock

Calculates time intervals using the timezone of a specified time value and returns the start of the interval nearest to the specified timestamp. Use date_bin_wallclock to downsample time series data by grouping rows into time-based "bins" or "windows" that are based off "wall clock" times in a specific timezone and applying an aggregate or selector function to each window.

Time zone shifts

Many regions use time zone shifts (such as daylight saving time (DST)). If a wall clock time bin starts at a time that does not exist in the specified time zone, the timestamp is adjusted to the time that is the same offset from the start of the day in that time zone.

If a wall clock time represents an ambiguous time in the region then the behavior depends on the size of the specified interval. If the interval is larger than the difference between the two possible timestamps, then the earlier timestamp is used. Otherwise, the function uses the timestamp that matches the UTC offset of the input timestamp.

date_bin_wallclock(interval, expression[, origin_timestamp])

Arguments

• interval: Bin interval. Supports the following interval units:

  • nanoseconds
  • microseconds
  • milliseconds
  • seconds
  • minutes
  • hours
  • days
  • weeks

  [!Note] date_bin_wallclock does not support month-, year-, or century-based intervals.

• expression: Time expression to operate on. Can be a constant, column, or function. The output timestamp uses the time zone from this time expression.

• origin_timestamp: Starting point used to determine bin boundaries. This must be a "wall clock" timestamp (no time zone). Default is the Unix epoch.

  [!Important]

  Avoid bins in time zone discontinuities

  Time zone shifts result in discontinuities–breaks in the continuity of time intervals (losing an hour or gaining an hour)–that can result in unexpected timestamps when using date_bin_wallclock. Avoid using an interval and origin_timestamp combination that results in a bin falling inside a time discontinuity.

  As a general rule, use either the default origin_timestamp or an origin timestamp with an offset relative to the Unix epoch that is equal to your specified interval.

  {{< expand-wrapper >}} {{% expand "View time zone discontinuity example" %}}

The following query illustrates how two timestamps, only one minute apart, result in timestamps two hours apart when binned across a daylight saving boundary:

SELECT
  tz('2020-10-25T02:29:00+01:00', 'Europe/Paris') AS original_time,
  date_bin_wallclock(
    INTERVAL '1 hour',
    tz('2020-10-25T02:29:00+01:00', 'Europe/Paris'),
    '1970-01-01T00:30:00'
  ) AT TIME ZONE 'UTC' AS utc_bin_time
UNION
SELECT
  tz('2020-10-25T02:30:00+01:00', 'Europe/Paris') AS original_time,
  date_bin_wallclock(
    INTERVAL '1 hour',
    tz('2020-10-25T02:30:00+01:00', 'Europe/Paris'),
    '1970-01-01T00:30:00'
  ) AT TIME ZONE 'UTC' AS utc_bin_time
ORDER BY original_time;

{{% /expand %}} {{< /expand-wrapper >}}

{{< expand-wrapper >}} {{% expand "View date_bin_wallclock query example" %}}

The following query uses the sample data set provided in the Get started with InfluxDB tutorial and returns the 12-hour average temperature for each room using times in the America/Los_Angeles time zone.

{{% influxdb/custom-timestamps %}}

SELECT
  date_bin_wallclock(INTERVAL '12 hours', tz(time, 'America/Los_Angeles')) AS time,
  room,
  avg(temp) AS avg_temp
FROM home
WHERE
    time >= '2022-01-01T08:00:00Z'
    AND time <= '2022-01-01T20:00:00Z'
GROUP BY 1, room

{{% /influxdb/custom-timestamps %}}

{{% /expand %}} {{< /expand-wrapper >}}

date_bin_wallclock_gapfill

Calculates time intervals using the timezone of a specified time value and returns the start of the interval nearest to the specified timestamp. If no rows exist in a time interval, a new row is inserted with a time value set to the interval start time, all columns in the GROUP BY clause populated, and null values in aggregate columns.

Use date_bin_wallclock_gapfill with interpolate or locf to fill gaps in data at specified time intervals in a specified time zone.

Time zone shifts

Many regions use time zone shifts (such as daylight saving time (DST)). If a wall clock time bin starts at a time that does not exist in the specified time zone, the timestamp is adjusted to the time that is the same offset from the start of the day in that time zone.

If a wall clock time represents an ambiguous time in the region then the behavior depends on the size of the specified interval. If the interval is larger than the difference between the two possible timestamps, then the earlier timestamp is used. Otherwise, the function uses the timestamp that matches the UTC offset of the input timestamp.

date_bin_wallclock_gapfill(interval, expression[, origin_timestamp])

[!Note] date_bin_wallclock_gapfill requires time bounds in the WHERE clause.

Arguments

• interval: Bin interval. Supports the following interval units:

  • nanoseconds
  • microseconds
  • milliseconds
  • seconds
  • minutes
  • hours
  • days
  • weeks

  [!Note] date_bin_wallclock_gapfill does not support month-, year-, or century-based intervals.

• expression: Time expression to operate on. Can be a constant, column, or function. The output timestamp uses the time zone from this time expression.

• origin_timestamp: Starting point used to determine bin boundaries. This must be a "wall clock" timestamp (no time zone). Default is the Unix epoch.

  [!Important]

  Avoid bins in time zone discontinuities

  Time zone shifts result in discontinuities–breaks in the continuity of time intervals (losing an hour or gaining an hour)–that can result in unexpected timestamps when using date_bin_wallclock_gapfill. Avoid using an interval and origin_timestamp combination that results in a bin falling inside a time discontinuity.

  As a general rule, use either the default origin_timestamp or an origin timestamp with an offset relative to the Unix epoch that is equal to your specified interval.

  View time zone discontinuity example

Related functions

interpolate, locf

{{< expand-wrapper >}} {{% expand "Use date_bin_wallclock_gapfill to insert rows when no rows exists" %}}

The following example uses the sample data set provided in the Get started with InfluxDB tutorial.

{{% influxdb/custom-timestamps %}}

SELECT
  date_bin_wallclock_gapfill(INTERVAL '30 minutes', tz(time, 'America/Los_Angeles')) as time,
  room,
  avg(temp) as temp
FROM home
WHERE
    time >= '2022-01-01T08:00:00Z'
    AND time <= '2022-01-01T10:00:00Z'
GROUP BY 1, room

{{% /influxdb/custom-timestamps %}} {{% /expand %}}

{{% expand "Use date_bin_wallclock_gapfill to fill gaps in data" %}}

Use interpolate and locf to fill the null values in rows inserted by date_bin_wallclock_gapfill.

The following examples use the sample data set provided in the Get started with InfluxDB tutorial.

{{< tabs-wrapper >}} {{% tabs "small" %}} interpolate locf {{% /tabs %}} {{% tab-content %}}

The example below uses interpolate to fill null values by interpolating values between non-null values.

{{% influxdb/custom-timestamps %}}

SELECT
  date_bin_wallclock_gapfill(INTERVAL '30 minutes', tz(time, 'America/Los_Angeles')) as time,
  room,
  interpolate(avg(temp))
FROM home
WHERE
    time >= '2022-01-01T08:00:00Z'
    AND time <= '2022-01-01T10:00:00Z'
GROUP BY 1, room

{{% /influxdb/custom-timestamps %}}

{{% /tab-content %}} {{% tab-content %}}

The example below uses locf to fill null values by carrying the last observed value forward.

{{% influxdb/custom-timestamps %}}

SELECT
  date_bin_wallclock_gapfill(INTERVAL '30 minutes', tz(time, 'America/Los_Angeles')) as time,
  room,
  locf(avg(temp))
FROM home
WHERE
    time >= '2022-01-01T08:00:00Z'
    AND time <= '2022-01-01T10:00:00Z'
GROUP BY 1, room

{{% /influxdb/custom-timestamps %}}

{{% /tab-content %}} {{< /tabs-wrapper >}}

{{% /expand %}} {{< /expand-wrapper >}}

date_trunc

Truncates a timestamp value to a specified precision.

date_trunc(precision, expression) 

Arguments

• precision: Time precision to truncate to. The following precisions are supported:

  • year
  • month
  • week
  • day
  • hour
  • minute
  • second

• expression: Time expression to operate on. Can be a constant, column, or function.

Aliases

• datetrunc

{{< expand-wrapper >}} {{% expand "View date_trunc query examples" %}}

Use date_trunc to return hourly averages

SELECT
  avg(water_level) AS level,
  date_trunc('hour', time) AS hour
FROM h2o_feet
WHERE
  time >= timestamp '2019-09-10T00:00:00Z'
  AND time <= timestamp '2019-09-12T00:00:00Z'
GROUP BY hour
ORDER BY hour

Use date_trunc to return weekly averages

SELECT
  mean(water_level) as level,
  date_trunc('week',time) AS week
FROM h2o_feet
WHERE
  time >= timestamp '2019-08-01T00:00:00Z'
  AND time <= timestamp '2019-10-31T00:00:00Z'
GROUP BY week
ORDER BY week

{{% /expand %}} {{< /expand-wrapper >}}

datetrunc

Alias of date_trunc.

date_format

Alias of to_char.

date_part

Returns the specified part of the date as an integer.

date_part(part, expression)

Arguments

• part: Part of the date to return. The following date parts are supported:

  • year
  • month
  • week (week of the year)
  • day (day of the month)
  • hour
  • minute
  • second
  • millisecond
  • microsecond
  • nanosecond
  • dow (day of the week)
  • doy (day of the year)

• expression: Time expression to operate on. Can be a constant, column, or function.

Aliases

• datepart

{{< expand-wrapper >}} {{% expand "View date_part query examples" %}}

SELECT
  date_part('hour', time) AS hour,
  time,
  "level description", 
  location
FROM h2o_feet
WHERE
  time >= timestamp '2019-08-17T02:54:00Z'
  AND time <= timestamp '2019-08-17T03:06:00Z'
ORDER BY time

{{% /expand %}} {{< /expand-wrapper >}}

datepart

Alias of date_part.

extract

Returns a sub-field from a time value as an integer. Similar to date_part, but with different arguments.

extract(field FROM source)

Arguments

• field: Part or field of the date to return. The following date fields are supported:

  • year
  • month
  • week (week of the year)
  • day (day of the month)
  • hour
  • minute
  • second
  • millisecond
  • microsecond
  • nanosecond
  • dow (day of the week)
  • doy (day of the year)

• source: Source time expression to operate on. Can be a constant, column, or function.

{{< expand-wrapper >}} {{% expand "View extract query example" %}}

SELECT 
  extract(day from time) AS day
FROM 
  h2o_feet 
LIMIT 1

{{% /expand %}} {{< /expand-wrapper >}}

from_unixtime

Converts an integer (Unix timestamp in seconds) to a timestamp value. The underlying result is a timestamp (Timestamp(TimeUnit::Second, None)). If you output query results as JSON (default for the API), CSV, or pretty (default for the CLI), the timestamp is formatted as an ISO 8601 string (YYYY-MM-DDTHH:MM:SS, without a timezone indicator). When output to Parquet, the raw integer value (for example, 1641042000) is preserved.

from_unixtime(expression)

Arguments

• expression: Integer expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.

Related functions

to_unixtime

{{< expand-wrapper >}} {{% expand "View from_unixtime query example" %}}

SELECT
  from_unixtime(1672531200000000000) AS RFC3339

{{% /expand %}} {{< /expand-wrapper >}}

make_date

Returns a date using the component parts (year, month, day).

[!Note] make_date returns a DATE32 Arrow type, which isn't supported by InfluxDB. To use with InfluxDB, cast the return value to a timestamp or string.

make_date(year, month, day)

Arguments

• year: Year to use when making the date. Can be a constant, column or function, and any combination of arithmetic operators.
• month: Month to use when making the date. Can be a constant, column or function, and any combination of arithmetic operators.
• day: Day to use when making the date. Can be a constant, column or function, and any combination of arithmetic operators

{{< expand-wrapper >}} {{% expand "View make_date query example" %}}

SELECT make_date(2024, 01, 01)::STRING AS date

{{% /expand %}} {{< /expand-wrapper >}}

now

Returns the current UTC timestamp.

The now() return value is determined at query time and returns the same timestamp, no matter when in the query plan the function executes.

now()

Aliases

• current_timestamp

{{< expand-wrapper >}} {{% expand "View now query example" %}}

SELECT
  "water_level",
  "time"
FROM h2o_feet
WHERE
  time <= now() - interval '12 minutes'

{{% /expand %}} {{< /expand-wrapper >}}

today

Alias of current_date.

to_char

Returns the string representation of a date, time, timestamp, or duration based on a Rust Chrono format string.

[!Note] Unlike the PostgreSQL TO_CHAR() function, this function does not support numeric formatting.

to_char(expression, format)

Arguments

• expression: Expression to operate on. Can be a constant, column, or function that results in a date, time, timestamp or duration.
• format: Rust Chrono format string to use to convert the expression.

Aliases

• date_format

{{< expand-wrapper >}} {{% expand "View to_char query example" %}}

SELECT
  to_char('2024-01-01T12:22:01Z'::TIMESTAMP, '%a %e-%b-%Y %H:%M:%S') AS datestring

{{% /expand %}} {{< /expand-wrapper >}}

to_date

Converts a value to a date (YYYY-MM-DD). Supports strings and numeric types as input. Strings are parsed as YYYY-MM-DD unless another format is specified. Numeric values are interpreted as days since the Unix epoch.

[!Note] to_date returns a DATE32 Arrow type, which isn't supported by InfluxDB. To use with InfluxDB, cast the return value to a timestamp or string.

to_date(expression[, ..., format_n])

Arguments

• expression: Expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.
• format_n: Optional Rust strftime pattern to use to parse the string expression. Formats are attempted in the order that they appear. The function returns the timestamp from the first format to parse successfully. If no formats parse successfully, the function returns an error.

{{< expand-wrapper >}} {{% expand "View to_date query example" %}}

SELECT
  to_date('1-Jan-2024', '%e-%b-%Y')::STRING AS date

{{% /expand %}} {{< /expand-wrapper >}}

to_local_time

Converts a timestamp with a timezone to a timestamp without a timezone (no offset or timezone information). This function accounts for time shifts like daylight saving time (DST).

[!Note] Use to_local_time() with date_bin() and date_bin_gapfill to generate window boundaries based the local time zone rather than UTC.

to_local_time(expression)

Arguments

• expression: Time expression to operate on. Can be a constant, column, or function.

{{< expand-wrapper >}} {{% expand "View to_local_time query example" %}}

SELECT
  to_local_time('2024-01-01 00:00:00'::TIMESTAMP) AS "local time";

{{% /expand %}} {{% expand "View to_local_time query example with a time zone offset" %}}

SELECT
  to_local_time((arrow_cast('2024-01-01 00:00:00', 'Timestamp(Nanosecond, Some("UTC"))')) AT TIME ZONE 'America/Los_Angeles') AS "local time"

{{% /expand %}} {{% expand "View to_local_time query example with date_bin" %}}

SELECT
  date_bin(interval '1 day', time, to_local_time(0::TIMESTAMP)) AT TIME ZONE 'America/Los_Angeles' AS time,
  avg(f1),
  avg(f2)
FROM
  (VALUES (arrow_cast('2024-01-01 12:00:00', 'Timestamp(Nanosecond, Some("UTC"))'), 1.23, 4.56),
          (arrow_cast('2024-01-01 13:00:00', 'Timestamp(Nanosecond, Some("UTC"))'), 2.46, 8.1),
          (arrow_cast('2024-01-01 14:00:00', 'Timestamp(Nanosecond, Some("UTC"))'), 4.81, 16.2)
  ) AS data(time, f1, f2)
GROUP BY 1

{{% /expand %}} {{< /expand-wrapper >}}

to_timestamp

Converts a value to RFC3339 timestamp format (YYYY-MM-DDT00:00:00Z). Supports timestamp, integer, and unsigned integer types as input. Integers and unsigned integers are parsed as Unix nanosecond timestamps and return the corresponding RFC3339 timestamp.

to_timestamp(expression)

Arguments

• expression: Expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.

{{< expand-wrapper >}} {{% expand "View to_timestamp query example" %}}

SELECT to_timestamp(1704067200000000000)

{{% /expand %}} {{< /expand-wrapper >}}

to_timestamp_micros

Converts a value to RFC3339 microsecond timestamp format (YYYY-MM-DDT00:00:00.000000Z). Supports timestamp, integer, and unsigned integer types as input. Integers and unsigned integers are parsed as Unix microsecond timestamps and return the corresponding RFC3339 timestamp.

to_timestamp_micros(expression[, ..., format_n])

Arguments

• expression: Expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.
• format_n: Optional Rust strftime pattern to use to parse the string expression. Formats are attempted in the order that they appear. The function returns the timestamp from the first format to parse successfully. If no formats parse successfully, the function returns an error.

{{< expand-wrapper >}} {{% expand "View to_timestamp_micros query example" %}}

SELECT to_timestamp_micros(1704067200000001)

SELECT to_timestamp_micros('01:01:59.123456789 01-01-2024', '%c', '%+', '%H:%M:%S%.f %m-%d-%Y') AS microsecond

{{% /expand %}} {{< /expand-wrapper >}}

to_timestamp_millis

Converts a value to RFC3339 millisecond timestamp format (YYYY-MM-DDT00:00:00.000Z). Supports timestamp, integer, and unsigned integer types as input. Integers and unsigned integers are parsed as Unix millisecond timestamps and return the corresponding RFC3339 timestamp.

to_timestamp_millis(expression[, ..., format_n])

Arguments

• expression: Expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.
• format_n: Optional Rust strftime pattern to use to parse the string expression. Formats are attempted in the order that they appear. The function returns the timestamp from the first format to parse successfully. If no formats parse successfully, the function returns an error.

{{< expand-wrapper >}} {{% expand "View to_timestamp_millis query example" %}}

SELECT to_timestamp_millis(1704067200001) AS time

Results

{{% /expand %}} {{% expand "View to_timestamp_millis example with string format parsing" %}}

SELECT to_timestamp_millis('01:01:59.123456789 01-01-2024', '%c', '%+', '%H:%M:%S%.f %m-%d-%Y') AS millisecond

{{% /expand %}} {{< /expand-wrapper >}}

to_timestamp_nanos

Converts a value to RFC3339 nanosecond timestamp format (YYYY-MM-DDT00:00:00.000000000Z). Supports timestamp, integer, and unsigned integer types as input. Integers and unsigned integers are parsed as Unix nanosecond timestamps and return the corresponding RFC3339 timestamp.

to_timestamp_nanos(expression[, ..., format_n])

Arguments

• expression: Expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.
• format_n: Optional Rust strftime pattern to use to parse the string expression. Formats are attempted in the order that they appear. The function returns the timestamp from the first format to parse successfully. If no formats parse successfully, the function returns an error.

{{< expand-wrapper >}} {{% expand "View to_timestamp_nanos query example" %}}

SELECT to_timestamp_nanos(1704067200000000001)

SELECT to_timestamp_nanos('01:01:59.123456789 01-01-2024', '%c', '%+', '%H:%M:%S%.f %m-%d-%Y') AS nanosecond

{{% /expand %}} {{< /expand-wrapper >}}

to_timestamp_seconds

Converts a value to RFC3339 second timestamp format (YYYY-MM-DDT00:00:00Z). Supports timestamp, integer, and unsigned integer types as input. Integers and unsigned integers are parsed as Unix second timestamps and return the corresponding RFC3339 timestamp.

to_timestamp_seconds(expression[, ..., format_n]) 

Arguments

• expression: Expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.
• format_n: Optional Rust strftime pattern to use to parse the string expression. Formats are attempted in the order that they appear. The function returns the timestamp from the first format to parse successfully. If no formats parse successfully, the function returns an error.

{{< expand-wrapper >}} {{% expand "View to_timestamp_seconds query example" %}}

SELECT to_timestamp_seconds(1704067201)

{{% /expand %}} {{% expand "View to_timestamp_seconds example with string format parsing" %}}

SELECT to_timestamp_seconds('01:01:59.123456789 01-01-2024', '%c', '%+', '%H:%M:%S%.f %m-%d-%Y') AS second

{{% /expand %}} {{< /expand-wrapper >}}

to_unixtime

Converts a value to seconds since the Unix epoch. Supports strings, timestamps, and floats as input. Strings are parsed as RFC3339Nano timestamps if no Rust Chrono format strings are provided.

to_unixtime(expression[, ..., format_n])

Arguments

• expression: Expression to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.
• format_n: Optional Rust strftime pattern to use to parse the string expression. Formats are attempted in the order that they appear. The function returns the timestamp from the first format to parse successfully. If no formats parse successfully, the function returns an error.

Related functions

from_unixtime

{{< expand-wrapper >}} {{% expand "View to_unixtime query example" %}}

SELECT to_unixtime('2024-01-01T01:01:59.123456789Z') AS unixtime

{{% /expand %}} {{% expand "View to_unixtime example with string format parsing" %}}

SELECT
  to_unixtime('01:01:59.123456789 01-01-2024', '%c', '%+', '%H:%M:%S%.f %m-%d-%Y') AS unixtime

{{% /expand %}} {{< /expand-wrapper >}}

tz

Converts a timestamp to a provided timezone. If the second argument is not provided, it defaults to UTC.

tz(time_expression[, timezone])

Arguments

• time_expression: time to operate on. Can be a constant, column, or function, and any combination of arithmetic operators.
• timezone: Timezone string to cast the value into. Default is 'UTC'. The function returns the timestamp cast to the specified timezone. If an incorrect timezone string is passed or the wrong datatype is provided, the function returns an error.

{{< expand-wrapper >}} {{% expand "View tz query example" %}}

SELECT tz('2024-01-01T01:00:00Z', 'America/New_York') AS time_tz

{{% /expand %}} {{% expand "View tz query example from Getting Started data" %}}

SELECT tz(time, 'Australia/Sydney') AS time_tz, time FROM home ORDER BY time LIMIT 3;

{{% /expand %}} {{< /expand-wrapper >}}

Differences between tz and AT TIME ZONE

tz and AT TIME ZONE differ when the input timestamp does not have a timezone.

• When using an input timestamp that does not have a timezone (the default behavior in InfluxDB) with the AT TIME ZONE operator, the operator returns the same timestamp, but with a timezone offset (also known as the "wall clock" time)--for example:

  sqlCopy

  '2024-01-01 00:00:00'::TIMESTAMP AT TIME ZONE 'America/Los_Angeles'
  
  -- Returns
  2024-01-01T00:00:00-08:00
  

• When using an input timestamp with a timezone, both the tz() function and the AT TIME ZONE operator return the timestamp converted to the time in the specified timezone--for example:

  sqlCopy

  '2024-01-01T00:00:00-00:00' AT TIME ZONE 'America/Los_Angeles'
  tz('2024-01-01T00:00:00-00:00', 'America/Los_Angeles')
  
  -- Both return
  2023-12-31T16:00:00-08:00
  

• tz() always converts the input timestamp to the specified time zone. If the input timestamp does not have a timezone, the function assumes it is a UTC timestamp--for example:

  sqlCopy

  tz('2024-01-01 00:00:00'::TIMESTAMP, 'America/Los_Angeles')
  -- Returns
  2023-12-31T16:00:00-08:00
  

  sqlCopy

  tz('2024-01-01T00:00:00+1:00', 'America/Los_Angeles')
  -- Returns
  2023-12-31T15:00:00-08:00
  

{{< expand-wrapper >}} {{% expand "View tz and ::timestamp comparison" %}}

SELECT
  '2024-04-01T00:00:20Z'::timestamp AT TIME ZONE 'Europe/Brussels' as time_timestamp,
  tz('2024-04-01T00:00:20', 'Europe/Brussels') as time_tz;