OpenText Analytics Database 26.2.x – Date/time data types

Sql-Reference: DATE

Mon, 01 Jan 0001 00:00:00 +0000

Consists of a month, day, and year. The following limits apply:

Lowest value: ~ 25e+15 BC
Higest value: ~ 25e+15 AD
Resolution: 1 DAY

See SET DATESTYLE for information about ordering.

Note

'0000-00-00' is not valid. If you try to insert that value into a DATE or TIMESTAMP field, an error occurs. If you copy '0000-00-00' into a DATE or TIMESTAMP field, OpenText™ Analytics Database converts the value to 0001-01-01 00:00:00 BC.

Syntax

DATE

Examples

Example	Description
`January 8, 1999`	Unambiguous in any `datestyle` input mode
`1999-01-08`	ISO 8601; January 8 in any mode (recommended format)
`1/8/1999`	January 8 in `MDY` mode; August 1 in `DMY` mode
`1/18/1999`	January 18 in `MDY` mode; rejected in other modes
`01/02/03`	January 2, 2003 in `MDY` mode February 1, 2003 in `DMY` mode February 3, 2001 in `YMD` mode
`1999-Jan-08`	January 8 in any mode
`Jan-08-1999`	January 8 in any mode
`08-Jan-1999`	January 8 in any mode
`99-Jan-08`	January 8 in `YMD` mode, else error
`08-Jan-99`	January 8, except error in `YMD` mode
`Jan-08-99`	January 8, except error in `YMD` mode
`19990108`	ISO 8601; January 8, 1999 in any mode
`990108`	ISO 8601; January 8, 1999 in any mode
`1999.008`	Year and day of year
`J2451187`	Julian day
`January 8, 99 BC`	Year 99 before the Common Era

Sql-Reference: DATETIME

Mon, 01 Jan 0001 00:00:00 +0000

DATETIME is an alias for TIMESTAMP/TIMESTAMPTZ.

Sql-Reference: INTERVAL

Mon, 01 Jan 0001 00:00:00 +0000

Measures the difference between two points in time. Intervals can be positive or negative. The INTERVAL data type is SQL:2008 compliant, and supports interval qualifiers that are divided into two major subtypes:

Year-month: Span of years and months
Day-time: Span of days, hours, minutes, seconds, and fractional seconds

Intervals are represented internally as some number of microseconds and printed as up to 60 seconds, 60 minutes, 24 hours, 30 days, 12 months, and as many years as necessary. You can control the output format of interval units with SET INTERVALSTYLE and SET DATESTYLE.

Syntax

INTERVAL 'interval-literal' [ interval-qualifier ] [ (p) ]

Parameters

interval-literal

A character string that expresses an interval, conforming to this format:

[-] { quantity subtype-unit }[...] [ AGO ]

For details, see Interval literal.

interval-qualifier

Optionally specifies how to interpret and format an interval literal for output, and, optionally, sets precision. If omitted, the default is DAY TO SECOND(6). For details, see Interval qualifier.

p

Specifies precision of the seconds field, where p is an integer between 0 - 6. For details, see Specifying interval precision.

Default: 6

Limits

Name	Low Value	High Value	Resolution
`INTERVAL DAY TO SECOND [(``p``)]`	`-106751991 days 04:00:54.775807`	`+/-106751991 days 04:00:54.775807`	1 microsecond
`INTERVAL YEAR TO MONTH`	`~/ -768e15 yrs`	`~ 768e15 yrs`	1 month

Sql-Reference: SMALLDATETIME

Mon, 01 Jan 0001 00:00:00 +0000

SMALLDATETIME is an alias for TIMESTAMP/TIMESTAMPTZ.

Sql-Reference: TIME/TIMETZ

Mon, 01 Jan 0001 00:00:00 +0000

Stores the specified time of day. TIMETZ is the same as TIME WITH TIME ZONE: both data types store the UTC offset of the specified time.

Syntax

TIME [ (p) ] [ { WITHOUT | WITH } TIME ZONE ] 'input-string' [ AT TIME ZONE zone ]

Parameters

p: Optional precision value that specifies the number of fractional digits retained in the seconds field, an integer value between 0 and 6. If you omit specifying precision, OpenText™ Analytics Database returns up to 6 fractional digits.
WITHOUT TIME ZONE: Ignore any time zone in the input string and use a value without a time zone (default).
WITH TIME ZONE: Convert the time to UTC. If the input string includes a time zone, use its UTC offset for the conversion. If the input string omits a time zone, the database uses the UTC offset of the time zone that is configured for your system.
input-string: See Input String below.
AT TIME ZONE zone: See TIME AT TIME ZONE and TIMESTAMP AT TIME ZONE.

TIMETZ vs. TIMESTAMPTZ

TIMETZ and TIMESTAMPTZ are not parallel SQL constructs. TIMESTAMPTZ records a time and date in GMT, converting from the specified TIME ZONE.TIMETZ records the specified time and the specified time zone, in minutes, from GMT.

Limits

Name	Low Value	High Value	Resolution
`TIME [``p``]`	`00:00:00.00`	`23:59:60.999999`	`1 µs`
`TIME [``p``] WITH TIME ZONE`	`00:00:00.00+14`	`23:59:59.999999-14`	`1 µs`

Input string

A TIME input string can be set to any of the formats shown below:

Example	Description
`04:05:06.789`	ISO 8601
`04:05:06`	ISO 8601
`04:05`	ISO 8601
`040506`	ISO 8601
`04:05 AM`	Same as 04:05; AM does not affect value
`04:05 PM`	Same as 16:05
`04:05:06.789-8`	ISO 8601
`04:05:06-08:00`	ISO 8601
`04:05-08:00`	ISO 8601
`040506-08`	ISO 8601
`04:05:06 PST`	Time zone specified by name

Data type coercion

You can cast a TIME or TIMETZ interval to a TIMESTAMP. This returns the local date and time as follows:

=> SELECT (TIME '3:01am')::TIMESTAMP;
       ?column?
---------------------
 2012-08-30 03:01:00
(1 row)

=> SELECT (TIMETZ '3:01am')::TIMESTAMP;
      ?column?
---------------------
 2012-08-22 03:01:00
(1 row)

Casting the same TIME or TIMETZ interval to a TIMESTAMPTZ returns the local date and time, appended with the UTC offset—in this example, -05:

=> SELECT (TIME '3:01am')::TIMESTAMPTZ;
        ?column?
------------------------
 2016-12-08 03:01:00-05
(1 row)

Sql-Reference: TIME AT TIME ZONE

Mon, 01 Jan 0001 00:00:00 +0000

Converts the specified TIME to the time in another time zone.

Syntax

TIME [WITH TIME ZONE] 'input-string' AT TIME ZONE 'zone'

Parameters

WITH TIME ZONE

Converts the input string to UTC, using the UTC offset for the specified time zone. If the input string omits a time zone, OpenText™ Analytics Database uses the UTC offset of the time zone configured for your system and converts the input string accordingly

zone

Specifies the time zone to use in the conversion, either as a literal or interval that specifies UTC offset:

AT TIME ZONE INTERVAL 'utc-offset'
AT TIME ZONE 'time-zone-literal'

For details, see Specifying Time Zones below.

Note

The database treats literals TIME ZONE and TIMEZONE as synonyms.

Specifying time zones

You can specify time zones in two ways:

A string literal such as America/Chicago or PST
An interval that specifies a UTC offset—for example, INTERVAL '-08:00'

It is generally good practice to specify time zones with literals that indicate a geographic location. OpenText™ Analytics Database makes the necessary seasonal adjustments, and thereby avoids inconsistent results. For example, the following two queries are issued when daylight time is in effect. Because the local UTC offset during daylight time is -04, both queries return the same results:

=> SELECT CURRENT_TIME(0) "EDT";
     EDT
-------------
 12:34:35-04
(1 row)

=> SELECT CURRENT_TIME(0) AT TIME ZONE 'America/Denver' "Mountain Time";
 Mountain Time
---------------
 10:34:35-06
(1 row)
=> SELECT CURRENT_TIME(0) AT TIME ZONE INTERVAL '-06:00' "Mountain Time";
 Mountain Time
---------------
 10:34:35-06
(1 row)

If you issue a use the UTC offset in a similar query when standard time is in effect, you must adjust the UTC offset accordingly—for Denver time, to -07—otherwise, OpenText™ Analytics Database returns a different (and erroneous) result:

=> SELECT CURRENT_TIME(0) "EST";
     EST
-------------
 14:18:22-05
(1 row)

=> SELECT CURRENT_TIME(0) AT TIME ZONE INTERVAL '-06:00' "Mountain Time";
 Mountain Time
---------------
 13:18:22-06
(1 row)

You can show and set the session's time zone with SHOW TIMEZONE and SET TIME ZONE, respectively:

=> SHOW TIMEZONE;
   name   |     setting
----------+------------------
 timezone | America/New_York
(1 row)

=> SELECT CURRENT_TIME(0) "Eastern Daylight Time";
 Eastern Daylight Time
-----------------------
 12:18:24-04
(1 row)

=> SET TIMEZONE 'America/Los_Angeles';
SET

=> SELECT CURRENT_TIME(0) "Pacific Daylight Time";
 Pacific Daylight Time
-----------------------
 09:18:24-07
(1 row)

Time zone literals

To view the default list of valid literals, see the files in the following directory:

opt/vertica/share/timezonesets

For example:

$ cat Antarctica.txt
...
# src/timezone/tznames/Antarctica.txt
#

AWST    28800    # Australian Western Standard Time
                 #     (Antarctica/Casey)
                 #     (Australia/Perth)
...

NZST    43200    # New Zealand Standard Time
                 #     (Antarctica/McMurdo)
                 #     (Pacific/Auckland)
ROTT   -10800    # Rothera Time
                 #     (Antarctica/Rothera)
SYOT    10800    # Syowa Time
                 #     (Antarctica/Syowa)
VOST    21600    # Vostok time
                 #     (Antarctica/Vostok)

Examples

The following example assumes that local time is EST (Eastern Standard Time). The query converts the specified time to MST (mountain standard time):

=> SELECT CURRENT_TIME(0);
  timezone
-------------
 10:10:56-05
(1 row)

=> SELECT TIME '10:10:56' AT TIME ZONE 'America/Denver' "Denver Time";
 Denver Time
-------------
 08:10:56-07
(1 row)

The next example adds a time zone literal to the input string—in this case, Europe/Vilnius—and converts the time to MST:

=> SELECT TIME '09:56:13 Europe/Vilnius' AT TIME ZONE 'America/Denver';
 Denver Time
-------------
 00:56:13-07
(1 row)

Sql-Reference: TIMESTAMP/TIMESTAMPTZ

Mon, 01 Jan 0001 00:00:00 +0000

Stores the specified date and time. TIMESTAMPTZ is the same as TIMESTAMP WITH TIME ZONE: both data types store the UTC offset of the specified time.

TIMESTAMP is an alias for DATETIME and SMALLDATETIME.

Syntax

TIMESTAMP [ (p) ] [ { WITHOUT | WITH } TIME ZONE ] 'input-string' [AT TIME ZONE zone ]
TIMESTAMPTZ [ (p) ] 'input-string' [ AT TIME ZONE zone ]

Parameters

p

Optional precision value that specifies the number of fractional digits retained in the seconds field, an integer value between 0 and 6. If you omit specifying precision, OpenText™ Analytics Database returns up to 6 fractional digits.

WITHOUT TIME ZONE WITH TIME ZONE

Specifies whether to include a time zone with the stored value:

WITHOUT TIME ZONE (default): Specifiesthat input-string does not include a time zone. If the input string contains a time zone, OpenText™ Analytics Database ignores this qualifier. Instead, it conforms to WITH TIME ZONE behavior.
WITH TIME ZONE: Specifies to convert input-string to UTC, using the UTC offset for the specified time zone. If the input string omits a time zone, the database uses the UTC offset of the time zone that is configured for your system.

input-string

See Input String below.

AT TIME ZONE zone

See TIMESTAMP AT TIME ZONE.

Limits

In the following table, values are rounded. See Date/time data types for more detail.

Name	Low Value	High Value	Resolution
`TIMESTAMP [ (p) ] [ WITHOUT TIME ZONE ]`	`290279 BC`	`294277 AD`	`1 µs`
`TIMESTAMP [ (p) ] WITH TIME ZONE`	`290279 BC`	`294277 AD`	`1 µs`

Input string

The date/time input string concatenates a date and a time. The input string can include a time zone, specified as a literal such as America/Chicago, or as a UTC offset.

The following list represents typical date/time input variations:

1999-01-08 04:05:06
1999-01-08 04:05:06 -8:00
January 8 04:05:06 1999 PST

Note

0000-00-00 is invalid input. If you try to insert that value into a DATE or TIMESTAMP field, an error occurs. If you copy 0000-00-00 into a DATE or TIMESTAMP field, the database converts the value to 0001-01-01 00:00:00 BC.

The input string can also specify the calendar era, either AD (default) or BC. If you omit the calendar era, the database assumes the current calendar era (AD). The calendar era typically follows the time zone; however, the input string can include it in various locations. For example, the following queries return the same results:

=> SELECT TIMESTAMP WITH TIME ZONE 'March 1, 44 12:00 CET BC ' "Caesar's Time of Death EST";
 Caesar's Time of Death EST
----------------------------
 0044-03-01 06:00:00-05 BC
(1 row)

=> SELECT TIMESTAMP WITH TIME ZONE 'March 1, 44 12:00 BC CET' "Caesar's Time of Death EST";
 Caesar's Time of Death EST
----------------------------
 0044-03-01 06:00:00-05 BC
(1 row)

Examples

=> SELECT (TIMESTAMP '2014-01-17 10:00' - TIMESTAMP '2014-01-01');
 ?column?
----------
 16 10:00
(1 row)

=> SELECT (TIMESTAMP '2014-01-17 10:00' - TIMESTAMP '2014-01-01') / 7;
     ?column?
-------------------
 2 08:17:08.571429
(1 row)

=> SELECT TIMESTAMP '2009-05-29 15:21:00.456789'-TIMESTAMP '2009-05-28';
     ?column?
-------------------
 1 15:21:00.456789
(1 row)

=> SELECT (TIMESTAMP '2009-05-29 15:21:00.456789'-TIMESTAMP '2009-05-28')(3);
    ?column?
----------------
 1 15:21:00.457
(1 row)

=> SELECT '2017-03-18 07:00'::TIMESTAMPTZ(0) + INTERVAL '1.5 day';
        ?column?
------------------------
 2017-03-19 19:00:00-04
(1 row)

=> SELECT (TIMESTAMP '2014-01-17 10:00' - TIMESTAMP '2014-01-01') day;
 ?column?
----------
 16
(1 row)

=> SELECT cast((TIMESTAMP '2014-01-17 10:00' - TIMESTAMP '2014-01-01')
day as integer) / 7;
       ?column?
----------------------
 2.285714285714285714
(1 row)

=> SELECT floor((TIMESTAMP '2014-01-17 10:00' - TIMESTAMP '2014-01-01')
/ interval '7');
 floor
-------
     2
(1 row)

=> SELECT (TIMESTAMP '2009-05-29 15:21:00.456789'-TIMESTAMP '2009-05-28') second;
   ?column?
---------------
 141660.456789
(1 row)

=> SELECT (TIMESTAMP '2012-05-29 15:21:00.456789'-TIMESTAMP '2009-01-01') year;
 ?column?
----------
 3
(1 row)

=> SELECT (TIMESTAMP '2012-05-29 15:21:00.456789'-TIMESTAMP '2009-01-01') month;
 ?column?
----------
 40
(1 row)

=> SELECT (TIMESTAMP '2012-05-29 15:21:00.456789'-TIMESTAMP '2009-01-01')
year to month;
 ?column?
----------
 3-4
(1 row)

=> SELECT (TIMESTAMP '2012-05-29 15:21:00.456789'-TIMESTAMP '2009-01-01')
second(3);
   ?column?
---------------
 107536860.457
(1 row)

=> SELECT (TIMESTAMP '2012-05-29 15:21:00.456789'-TIMESTAMP '2009-01-01') minute;
 ?column?
----------
 1792281
(1 row)

=> SELECT (TIMESTAMP '2012-05-29 15:21:00.456789'-TIMESTAMP '2009-01-01')
minute to second(3);
    ?column?
----------------
 1792281:00.457
(1 row)

=> SELECT TIMESTAMP 'infinity';
 ?column?
----------
 infinity
(1 row)

Sql-Reference: TIMESTAMP AT TIME ZONE

Mon, 01 Jan 0001 00:00:00 +0000

Converts the specified TIMESTAMP or TIMESTAMPTZ (TIMESTAMP WITH TIMEZONE) to another time zone. OpenText™ Analytics Database executes AT TIME ZONE differently, depending on whether the date input is a TIMESTAMP or TIMESTAMPTZ. See TIMESTAMP versus TIMESTAMPTZ Behavior below.

Syntax

timestamp-clause AT TIME ZONE 'zone'

Parameters

[timestamp-clause](/en/sql-reference/data-types/datetime-data-types/timestamptimestamptz/)

Specifies the timestamp to convert, either TIMESTAMP or TIMESTAMPTZ.

For details, see TIMESTAMP/TIMESTAMPTZ.

AT TIME ZONE zone

Specifies the time zone to use in the timestamp conversion, where zone is a literal or interval that specifies a UTC offset:

AT TIME ZONE INTERVAL 'utc-offset'
AT TIME ZONE 'time-zone-literal'

For details, see Specifying Time Zones below.

Note

The database treats literals TIME ZONE and TIMEZONE as synonyms.

TIMESTAMP versus TIMESTAMPTZ behavior

How the database interprets AT TIME ZONE depends on whether the date input is a TIMESTAMP or TIMESTAMPTZ:

Date input Action

Date input	Action
`TIMESTAMP`	If the input string specifies no time zone, the database performs two actions: Converts the input string to the time zone of the `AT TIME ZONE` argument. Returns the time for the current session's time zone. If the input string includes a time zone, the database implicitly casts it to a `TIMESTAMPTZ` and converts it accordingly (see `TIMESTAMPTZ` below). For example, the following statement specifies a `TIMESTAMP` with no time zone. The database executes the statement as follows: Converts the input string to PDT (Pacific Daylight Time). Returns that time in the local time zone, which is three hours later: `=> SHOW TIMEZONE; name \| setting ----------+------------------ timezone \| America/New_York (1 row) SELECT TIMESTAMP '2017-3-14 5:30' AT TIME ZONE 'PDT'; timezone ------------------------ 2017-03-14 08:30:00-04 (1 row)`
`TIMESTAMPTZ`	The database converts the input string to the time zone of the `AT TIME ZONE` argument and returns that time. For example, the following statement specifies a `TIMESTAMPTZ` data type. The input string omits any time zone expression, so the database assumes the input string to be in local time zone (`America/New_York`) and returns the time of the `AT TIME ZONE` argument: `=> SHOW TIMEZONE; name \| setting ----------+------------------ timezone \| America/New_York (1 row) => SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40' AT TIME ZONE 'America/Denver'; timezone --------------------- 2001-02-16 18:38:40 (1 row)` The input string in the next statement explicitly specifies a time zone, so the database coerces the `TIMESTAMP` to a `TIMESTAMPTZ` and returns the time of the `AT TIME ZONE` argument: `=> SELECT TIMESTAMP '2001-02-16 20:38:40 America/Mexico_City' AT TIME ZONE 'Asia/Tokyo'; timezone --------------------- 2001-02-17 11:38:40 (1 row)`

TIMESTAMP

If the input string specifies no time zone, the database performs two actions:

Converts the input string to the time zone of the AT TIME ZONE argument.
Returns the time for the current session's time zone.

If the input string includes a time zone, the database implicitly casts it to a TIMESTAMPTZ and converts it accordingly (see TIMESTAMPTZ below).

For example, the following statement specifies a TIMESTAMP with no time zone. The database executes the statement as follows:

Converts the input string to PDT (Pacific Daylight Time).
Returns that time in the local time zone, which is three hours later:

=> SHOW TIMEZONE;
   name   |     setting
----------+------------------
 timezone | America/New_York
(1 row)

SELECT TIMESTAMP '2017-3-14 5:30' AT TIME ZONE 'PDT';
        timezone
------------------------
 2017-03-14 08:30:00-04
(1 row)

TIMESTAMPTZ

The database converts the input string to the time zone of the AT TIME ZONE argument and returns that time.

For example, the following statement specifies a TIMESTAMPTZ data type. The input string omits any time zone expression, so the database assumes the input string to be in local time zone (America/New_York) and returns the time of the AT TIME ZONE argument:

=> SHOW TIMEZONE;
   name   |     setting
----------+------------------
 timezone | America/New_York
(1 row)

=> SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40' AT TIME ZONE 'America/Denver';
      timezone
---------------------
 2001-02-16 18:38:40
(1 row)

The input string in the next statement explicitly specifies a time zone, so the database coerces the TIMESTAMP to a TIMESTAMPTZ and returns the time of the AT TIME ZONE argument:

=> SELECT TIMESTAMP '2001-02-16 20:38:40 America/Mexico_City' AT TIME ZONE 'Asia/Tokyo';
      timezone
---------------------
 2001-02-17 11:38:40
(1 row)

Specifying time zones

You can specify time zones in two ways:

A string literal such as America/Chicago or PST
An interval that specifies a UTC offset—for example, INTERVAL '-08:00'

=> SELECT TIMESTAMPTZ '2017-03-16 09:56:13' AT TIME ZONE 'America/Denver' "Denver Time";
     Denver Time
---------------------
 2017-03-16 07:56:13
(1 row)

=> SELECT TIMESTAMPTZ '2017-03-16 09:56:13' AT TIME ZONE INTERVAL '-06:00' "Denver Time";
     Denver Time
---------------------
 2017-03-16 07:56:13
(1 row)

=> SELECT TIMESTAMPTZ '2017-01-16 09:56:13' AT TIME ZONE 'America/Denver' "Denver Time";
     Denver Time
---------------------
 2017-0-16 07:56:13
(1 row)

=> SELECT TIMESTAMPTZ '2017-01-16 09:56:13' AT TIME ZONE INTERVAL '-06:00' "Denver Time";
     Denver Time
---------------------
 2017-01-16 08:56:13
(1 row)

You can show and set the session's time zone with SHOW TIMEZONE and SET TIME ZONE, respectively:

=> SHOW TIMEZONE;
   name   |     setting
----------+------------------
 timezone | America/New_York
(1 row)

=> SELECT CURRENT_TIMESTAMP(0) "Eastern Daylight Time";
 Eastern Daylight Time
------------------------
 2017-03-20 12:18:24-04
(1 row)

=> SET TIMEZONE 'America/Los_Angeles';
SET

=> SELECT CURRENT_TIMESTAMP(0) "Pacific Daylight Time";
 Pacific Daylight Time
------------------------
 2017-03-20 09:18:24-07
(1 row)

Time zone literals

To view the default list of valid literals, see the files in the following directory:

opt/vertica/share/timezonesets

For example:

$ cat Antarctica.txt
...
# src/timezone/tznames/Antarctica.txt
#

AWST    28800    # Australian Western Standard Time
                 #     (Antarctica/Casey)
                 #     (Australia/Perth)
...

NZST    43200    # New Zealand Standard Time
                 #     (Antarctica/McMurdo)
                 #     (Pacific/Auckland)
ROTT   -10800    # Rothera Time
                 #     (Antarctica/Rothera)
SYOT    10800    # Syowa Time
                 #     (Antarctica/Syowa)
VOST    21600    # Vostok time
                 #     (Antarctica/Vostok)

OpenText Analytics Database 26.2.x – Date/time data types

Sql-Reference: DATE

Note

Syntax

Examples

Sql-Reference: DATETIME

Sql-Reference: INTERVAL

Syntax

Parameters

Limits

Sql-Reference: SMALLDATETIME

Sql-Reference: TIME/TIMETZ

Syntax

Parameters

TIMETZ vs. TIMESTAMPTZ

Limits

Input string

Data type coercion

Sql-Reference: TIME AT TIME ZONE

Syntax

Parameters

Note

Specifying time zones

Time zone literals

Examples

See also

Sql-Reference: TIMESTAMP/TIMESTAMPTZ

Syntax

Parameters

Limits

Input string

Note

Examples

Sql-Reference: TIMESTAMP AT TIME ZONE

Syntax

Parameters

Note

TIMESTAMP versus TIMESTAMPTZ behavior

Specifying time zones

Time zone literals

See also