functions_datetime.yaml¶
This document file is generated for functions_datetime.yaml
Scalar Functions¶
extract¶
Implementations:
extract(component, x, timezone): -> return_type
0. extract(component, timestamp_tz, string): -> i64
1. extract(component, timestamp): -> i64
2. extract(component, date): -> i64
3. extract(component, time): -> i64
4. extract(component, indexing, timestamp_tz, string): -> i64
5. extract(component, indexing, timestamp): -> i64
6. extract(component, indexing, date): -> i64
Extract portion of a date/time value. * YEAR Return the year. * ISO_YEAR Return the ISO 8601 week-numbering year. First week of an ISO year has the majority (4 or more) of its days in January. * US_YEAR Return the US epidemiological year. First week of US epidemiological year has the majority (4 or more) of its days in January. Last week of US epidemiological year has the year’s last Wednesday in it. US epidemiological week starts on Sunday. * QUARTER Return the number of the quarter within the year. January 1 through March 31 map to the first quarter, April 1 through June 30 map to the second quarter, etc. * MONTH Return the number of the month within the year. * DAY Return the number of the day within the month. * DAY_OF_YEAR Return the number of the day within the year. January 1 maps to the first day, February 1 maps to the thirty-second day, etc. * MONDAY_DAY_OF_WEEK Return the number of the day within the week, from Monday (first day) to Sunday (seventh day). * SUNDAY_DAY_OF_WEEK Return the number of the day within the week, from Sunday (first day) to Saturday (seventh day). * MONDAY_WEEK Return the number of the week within the year. First week starts on first Monday of January. * SUNDAY_WEEK Return the number of the week within the year. First week starts on first Sunday of January. * ISO_WEEK Return the number of the ISO week within the ISO year. First ISO week has the majority (4 or more) of its days in January. ISO week starts on Monday. * US_WEEK Return the number of the US week within the US year. First US week has the majority (4 or more) of its days in January. US week starts on Sunday. * HOUR Return the hour (0-23). * MINUTE Return the minute (0-59). * SECOND Return the second (0-59). * MILLISECOND Return number of milliseconds since the last full second. * MICROSECOND Return number of microseconds since the last full millisecond. * SUBSECOND Return number of microseconds since the last full second of the given timestamp. * UNIX_TIME Return number of seconds that have elapsed since 1970-01-01 00:00:00 UTC, ignoring leap seconds. * TIMEZONE_OFFSET Return number of seconds of timezone offset to UTC. The range of values returned for QUARTER, MONTH, DAY, DAY_OF_YEAR, MONDAY_DAY_OF_WEEK, SUNDAY_DAY_OF_WEEK, MONDAY_WEEK, SUNDAY_WEEK, ISO_WEEK, and US_WEEK depends on whether counting starts at 1 or 0. This is governed by the indexing option. When indexing is ONE: * QUARTER returns values in range 1-4 * MONTH returns values in range 1-12 * DAY returns values in range 1-31 * DAY_OF_YEAR returns values in range 1-366 * MONDAY_DAY_OF_WEEK and SUNDAY_DAY_OF_WEEK return values in range 1-7 * MONDAY_WEEK, SUNDAY_WEEK, ISO_WEEK, and US_WEEK return values in range 1-53 When indexing is ZERO: * QUARTER returns values in range 0-3 * MONTH returns values in range 0-11 * DAY returns values in range 0-30 * DAY_OF_YEAR returns values in range 0-365 * MONDAY_DAY_OF_WEEK and SUNDAY_DAY_OF_WEEK return values in range 0-6 * MONDAY_WEEK, SUNDAY_WEEK, ISO_WEEK, and US_WEEK return values in range 0-52 The indexing option must be specified when the component is QUARTER, MONTH, DAY, DAY_OF_YEAR, MONDAY_DAY_OF_WEEK, SUNDAY_DAY_OF_WEEK, MONDAY_WEEK, SUNDAY_WEEK, ISO_WEEK, or US_WEEK. The indexing option cannot be specified when the component is YEAR, ISO_YEAR, US_YEAR, HOUR, MINUTE, SECOND, MILLISECOND, MICROSECOND, SUBSECOND, UNIX_TIME, or TIMEZONE_OFFSET. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.
Options:
extract_boolean¶
Implementations:
extract_boolean(component, x): -> return_type
0. extract_boolean(component, timestamp): -> boolean
1. extract_boolean(component, timestamp_tz, string): -> boolean
2. extract_boolean(component, date): -> boolean
*Extract boolean values of a date/time value. * IS_LEAP_YEAR Return true if year of the given value is a leap year and false otherwise. * IS_DST Return true if DST (Daylight Savings Time) is observed at the given value in the given timezone.
Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.*
Options:
add¶
Implementations:
add(x, y): -> return_type
0. add(timestamp, interval_year): -> timestamp
1. add(timestamp_tz, interval_year, string): -> timestamp_tz
2. add(date, interval_year): -> timestamp
3. add(timestamp, interval_day): -> timestamp
4. add(timestamp_tz, interval_day): -> timestamp_tz
5. add(date, interval_day): -> timestamp
Add an interval to a date/time type. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.
add_intervals¶
Implementations:
add_intervals(x, y): -> return_type
0. add_intervals(interval_day, interval_day): -> interval_day
1. add_intervals(interval_year, interval_year): -> interval_year
Add two intervals together.
subtract¶
Implementations:
subtract(x, y): -> return_type
0. subtract(timestamp, interval_year): -> timestamp
1. subtract(timestamp_tz, interval_year): -> timestamp_tz
2. subtract(timestamp_tz, interval_year, string): -> timestamp_tz
3. subtract(date, interval_year): -> date
4. subtract(timestamp, interval_day): -> timestamp
5. subtract(timestamp_tz, interval_day): -> timestamp_tz
6. subtract(date, interval_day): -> date
Subtract an interval from a date/time type. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.
lte¶
Implementations:
lte(x, y): -> return_type
0. lte(timestamp, timestamp): -> boolean
1. lte(timestamp_tz, timestamp_tz): -> boolean
2. lte(date, date): -> boolean
3. lte(interval_day, interval_day): -> boolean
4. lte(interval_year, interval_year): -> boolean
less than or equal to
lt¶
Implementations:
lt(x, y): -> return_type
0. lt(timestamp, timestamp): -> boolean
1. lt(timestamp_tz, timestamp_tz): -> boolean
2. lt(date, date): -> boolean
3. lt(interval_day, interval_day): -> boolean
4. lt(interval_year, interval_year): -> boolean
less than
gte¶
Implementations:
gte(x, y): -> return_type
0. gte(timestamp, timestamp): -> boolean
1. gte(timestamp_tz, timestamp_tz): -> boolean
2. gte(date, date): -> boolean
3. gte(interval_day, interval_day): -> boolean
4. gte(interval_year, interval_year): -> boolean
greater than or equal to
gt¶
Implementations:
gt(x, y): -> return_type
0. gt(timestamp, timestamp): -> boolean
1. gt(timestamp_tz, timestamp_tz): -> boolean
2. gt(date, date): -> boolean
3. gt(interval_day, interval_day): -> boolean
4. gt(interval_year, interval_year): -> boolean
greater than
assume_timezone¶
Implementations:
assume_timezone(x, timezone): -> return_type
0. assume_timezone(timestamp, string): -> timestamp_tz
1. assume_timezone(date, string): -> timestamp_tz
Convert local timestamp to UTC-relative timestamp_tz using given local time’s timezone. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.
local_timestamp¶
Implementations:
local_timestamp(x, timezone): -> return_type
0. local_timestamp(timestamp_tz, string): -> timestamp
Convert UTC-relative timestamp_tz to local timestamp using given local time’s timezone. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.
strptime_time¶
Implementations:
strptime_time(time_string, format): -> return_type
0. strptime_time(string, string): -> time
Parse string into time using provided format, see https://man7.org/linux/man-pages/man3/strptime.3.html for reference.
strptime_date¶
Implementations:
strptime_date(date_string, format): -> return_type
0. strptime_date(string, string): -> date
Parse string into date using provided format, see https://man7.org/linux/man-pages/man3/strptime.3.html for reference.
strptime_timestamp¶
Implementations:
strptime_timestamp(timestamp_string, format, timezone): -> return_type
0. strptime_timestamp(string, string, string): -> timestamp_tz
1. strptime_timestamp(string, string): -> timestamp_tz
Parse string into timestamp using provided format, see https://man7.org/linux/man-pages/man3/strptime.3.html for reference. If timezone is present in timestamp and provided as parameter an error is thrown. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is supplied as parameter and present in the parsed string the parsed timezone is used. If parameter supplied timezone is invalid an error is thrown.
strftime¶
Implementations:
strftime(x, format): -> return_type
0. strftime(timestamp, string): -> string
1. strftime(timestamp_tz, string, string): -> string
2. strftime(date, string): -> string
3. strftime(time, string): -> string
Convert timestamp/date/time to string using provided format, see https://man7.org/linux/man-pages/man3/strftime.3.html for reference. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.
round_temporal¶
Implementations:
round_temporal(x, rounding, unit, multiple, origin): -> return_type
0. round_temporal(timestamp, rounding, unit, i64, timestamp): -> timestamp
1. round_temporal(timestamp_tz, rounding, unit, i64, string, timestamp_tz): -> timestamp_tz
2. round_temporal(date, rounding, unit, i64, date): -> date
3. round_temporal(time, rounding, unit, i64, time): -> time
Round a given timestamp/date/time to a multiple of a time unit. If the given timestamp is not already an exact multiple from the origin in the given timezone, the resulting point is chosen as one of the two nearest multiples. Which of these is chosen is governed by rounding: FLOOR means to use the earlier one, CEIL means to use the later one, ROUND_TIE_DOWN means to choose the nearest and tie to the earlier one if equidistant, ROUND_TIE_UP means to choose the nearest and tie to the later one if equidistant. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.
Options:
round_calendar¶
Implementations:
round_calendar(x, rounding, unit, origin, multiple): -> return_type
0. round_calendar(timestamp, rounding, unit, origin, i64): -> timestamp
1. round_calendar(timestamp_tz, rounding, unit, origin, i64, string): -> timestamp_tz
2. round_calendar(date, rounding, unit, origin, i64, date): -> date
3. round_calendar(time, rounding, unit, origin, i64, time): -> time
Round a given timestamp/date/time to a multiple of a time unit. If the given timestamp is not already an exact multiple from the last origin unit in the given timezone, the resulting point is chosen as one of the two nearest multiples. Which of these is chosen is governed by rounding: FLOOR means to use the earlier one, CEIL means to use the later one, ROUND_TIE_DOWN means to choose the nearest and tie to the earlier one if equidistant, ROUND_TIE_UP means to choose the nearest and tie to the later one if equidistant. Timezone strings must be as defined by IANA timezone database (https://www.iana.org/time-zones). Examples: “Pacific/Marquesas”, “Etc/GMT+1”. If timezone is invalid an error is thrown.