InterSystems SQL Reference
TO_DATE
|
|
A date function that converts a formatted string to a date.
Synopsis
TO_DATE(date_string[,format])
TODATE(date_string[,format])
The names
TO_DATE and
TODATE are interchangeable and are supported for Oracle compatibility.
The
TO_DATE function converts date strings in various formats to a date integer value, with data type DATE. It is used to input dates in various string formats, storing them in a standard internal representation.
TO_DATE returns a date with the following format:
Where
nnnnn is a positive integer between 0 (December 31, 1840) and 2980013 (December 31, 9999), inclusive. This represents a count of days. Time values are ignored.
The default earliest date is December 31, 1840. You can change the DATE data type MINVAL parameter to permit negative integers representing dates prior to December 31, 1840, as described in the
Data Types reference page in this manual. Dates before December 31, 1840 can also be represented using Julian dates, as described below.
This function can also be invoked from ObjectScript using the
TODATE() method call:
The
TO_DATE function can be used in data definition when supplying a default value to a field. For example:
CREATE TABLE mytest
(ID NUMBER(12,0) NOT NULL,
End_Year DATE DEFAULT TO_DATE('12-31-2018','MM-DD-YYYY') NOT NULL)
-
TO_DATE converts a formatted date string to a date integer.
-
TO_CHAR performs the reverse operation; it converts a date integer to a formatted date string.
-
TO_TIMESTAMP converts a formatted date and time string to a standard timestamp.
-
The first argument specifies a date string literal. You can supply a date string of any kind for the input
date_string. Each character must correspond to the
format string, with the following exceptions:
-
Leading zeros may be included or omitted (with the exception of a
date_string without separator characters).
-
Years may be specified with two digits or four digits.
-
Month names may be specified in full or as the first three letters of the name. Only the first three letters must be correct. Month names are not case-sensitive.
-
Time values appended to a date are ignored.
The second argument specifies a date format as a string of code characters.
If you specify no
format,
TO_DATE parses the date string using the default format. The default format is DD MON YYYY. For example, '22 Feb 2018'.
This default format is configurable system-wide, using either:
A
format is a string of one or more format elements specified according to the following rules:
-
Format elements are not case-sensitive.
-
Almost any sequence or number of format elements is permitted.
-
Format strings separate their elements with non-alphanumeric separator characters (for example, a space, slash, or hyphen) that match the separator characters in the
date_string. This use of specified date separator characters does not depend on the DateSeparator defined for your NLS locale.
-
The following date format strings do not require separator characters:
MMDDYYYY,
DDMMYYYY,
YYYYMMDD, and
YYYYDDMM. The incomplete date format
YYYYMM is also supported, and assume a DD value of 01. Note that in these cases leading zeros must be provided for MM and DD values.
The following table lists the valid date format elements for the
format argument:
A
TO_DATE format can also include a D (day of week number), DY (day of week abbreviation), or DAY (day of week name) element. However, these format elements are not validated or used to determine the return value. For further details on these
format elements, refer to
TO_CHAR.
Date Formats for Single Date Elements
You can specify DD, DDD, MM, or YYYY as a complete date format. Because these
format strings omit the month, year, or both the month and year, InterSystems IRIS interprets them as referring to the current month and year:
-
DD returns the date for the specified day in the current month of the current year.
-
DDD returns the date for the specified day of the year in the current year.
-
MM returns the date for the first day of the specified month in the current year.
-
YYYY - returns the date for the first day of the current month of the specified year.
The following Embedded SQL examples show these formats:
NEW SQLCODE
&sql(SELECT
TO_DATE('300','DDD'),
TO_DATE('24','DD')
INTO :a,:b)
IF SQLCODE=0 {
WRITE "DDD format: ",a," = ",$ZDATE(a,1,,4),!
WRITE "DD format: ",b," = ",$ZDATE(b,1,,4) }
ELSE { WRITE "error:",SQLCODE }
NEW SQLCODE
&sql(SELECT
TO_DATE('8','MM'),
TO_DATE('2018','YYYY')
INTO :a,:b)
IF SQLCODE=0 {
WRITE "MM format: ",a," = ",$ZDATE(a,1,,4),!
WRITE "YYYY format: ",b," = ",$ZDATE(b,1,,4),!
WRITE "done" }
ELSE { WRITE "error:",SQLCODE }
Two-Digit Year Conversion (RR and RRRR formats)
The YY format converts a two-digit year value to four digits by simply appending 19. Thus 07 becomes 1907 and 93 becomes 1993.
The RR format provides more flexible two-digit to four-digit year conversion. This conversion is based on the current year. If the current year is in the first half of a century (for example, 2000 through 2050), two-digit years from 00 through 49 are expanded to a four-digit year in the current century, and two-digit years from 50 through 99 are expanded to a four-digit year in the previous century. If the current year is in the second half of a century (for example, 2050 through 2099), all two-digit years are expanded to a four-digit year in the current century. This expansion of two-digit years to four-digit years is shown in the following Embedded SQL example:
NEW SQLCODE
&sql(SELECT
TO_DATE('29 September 00','DD MONTH RR'),
TO_DATE('29 September 18','DD MONTH RR'),
TO_DATE('29 September 49','DD MONTH RR'),
TO_DATE('29 September 50','DD MONTH RR'),
TO_DATE('29 September 77','DD MONTH RR')
INTO :a,:b,:c,:d,:e)
IF SQLCODE=0 {
WRITE a," = ",$ZDATE(a,1,,4),!
WRITE b," = ",$ZDATE(b,1,,4),!
WRITE c," = ",$ZDATE(c,1,,4),!
WRITE d," = ",$ZDATE(d,1,,4),!
WRITE e," = ",$ZDATE(e,1,,4) }
ELSE { WRITE "error:",SQLCODE }
The RRRR format permits you to input a mix of two–digit and four-digit years. Four-digit years are passed through unchanged (the same as YYYY). Two-digit years are converted to four-digit years, using the RR format algorithm. This is shown in the following Embedded SQL example:
NEW SQLCODE
&sql(SELECT
TO_DATE('29 September 2018','DD MONTH RRRR'),
TO_DATE('29 September 18','DD MONTH RRRR'),
TO_DATE('29 September 1949','DD MONTH RRRR'),
TO_DATE('29 September 49','DD MONTH RRRR'),
TO_DATE('29 September 1950','DD MONTH RRRR'),
TO_DATE('29 September 50','DD MONTH RRRR')
INTO :a,:b,:c,:d,:e,:f)
IF SQLCODE=0 {
WRITE a," 4-digit = ",$ZDATE(a,1,,4),!
WRITE b," 2-digit = ",$ZDATE(b,1,,4),!
WRITE c," 4-digit = ",$ZDATE(c,1,,4),!
WRITE d," 2-digit = ",$ZDATE(d,1,,4),!
WRITE e," 4-digit = ",$ZDATE(e,1,,4),!
WRITE f," 2-digit = ",$ZDATE(f,1,,4) }
ELSE { WRITE "error:",SQLCODE }
Day of the Year (DDD format)
You can use DDD to convert the day of the year (number of days elapsed since January 1) to an actual date. The format string
DDD YYYY must be paired with a corresponding
date_string consisting of an integer number of days and a four-digit year. (Two-digit years must be specified as RR (not YY) when used with DDD.) The format string
DDD defaults to the current year. The number of elapsed days must be a positive integer in the range 1 through 365 (366 if YYYY is a leap year). The four-digit year must be within the standard InterSystems IRIS date range: 1841 through 9999. The DDD and YYYY format elements can be specified in any order; a separator character between them is mandatory. The following example shows this use of Day of the Year:
NEW SQLCODE
&sql(SELECT TO_DATE('2018:60','YYYY:DDD')
INTO :a)
IF SQLCODE=0 {WRITE a," = ",$ZDATE(a,1,,4) }
ELSE { WRITE "error:",SQLCODE }
If a format string contains both a DD and a DDD element, the DDD element is dominant. This is shown in the following example, which returns 2/29/2020 (not 12/31/2020):
NEW SQLCODE
&sql(SELECT TO_DATE('2020-12-31-60','YYYY-MM-DD-DDD')
INTO :a)
IF SQLCODE=0 {WRITE a," = ",$ZDATE(a,1,,4) }
ELSE { WRITE "error:",SQLCODE }
TO_DATE permits you to return a date expression corresponding to a day of the year.
TO_CHAR permits you to return the day of the year corresponding to a date expression.
In InterSystems SQL, a Julian date can be used for any date before December 31, 1840. Because InterSystems IRIS represents this date internally as 0, special syntax is needed to represent earlier dates.
TO_DATE provides a
format of 'J' (or 'j') for this purpose. Julian date conversion converts a seven-digit internal numeric value (a Julian day count) to a display-format or ODBC-format date. For example:
NEW SQLCODE
&sql(SELECT TO_DATE(2300000,'J')
INTO :a)
IF SQLCODE=0 {WRITE a }
ELSE { WRITE "error:",SQLCODE }
returns the following date:
1585–01–31 (ODBC format) or
01/31/1585 (display format). Julian day count 1721424 returns January 1st of the Year 1 (
1–01–01). Julian day counts such as 1709980 (battle of Actium marks beginning of Roman Empire under Augustus Caesar) return BCE (BC) dates, which are displayed with the year preceded by a minus sign.
Note:
By default, the %Date data type does not represent dates prior to
December 31, 1840. However, you can redefine the MINVAL parameter for this data type to permit representation of earlier dates as negative integers, with the limit of January 1, Year 1. This representation of dates as negative integers is not compatible with the “Julian” date format described here. For further details refer to the
Data Types reference page in this manual.
A Julian day count is always represented internally as a seven-digit number, with leading zeros when necessary.
TO_DATE allows you to input a Julian day count without the leading zeros. The highest permitted Julian date is 5373484, it returns
12/31/9999. The lowest permitted Julian date is 0000001, it returns
01/01/-4712 (which is BCE date 01/01/-4713). Any value outside this range generates an SQLCODE -400 error, with a %msg value of
“Invalid Julian Date value. Julian date must be between 1 and 5373484”.
Note:
The following consideration should not affect the interconversion of dates and Julian day counts using
TO_CHAR and
TO_DATE. It may affect some calculations made using Julian day counts.
Julian day counts prior to 1721424 (1/1/1) are compatible with other software implementations, such as Oracle. They are
not identical to BCE dates in ordinary usage. In ordinary usage, there is no Year 0; dates go from 12/31/-1 to 1/1/1. In Oracle usage, the Julian dates 1721058 through 1721423 are simply invalid, and return an error. In InterSystems IRIS, these Julian dates return the non-existent Year 0 as a place holder. Thus calculations involving BCE dates must be adjusted by one year to correspond to common usage.
Also be aware that these date counts do not take into account changes in date caused by the Gregorian calendar reform (enacted October 15, 1582, but not adopted in Britain and its colonies until 1752).
TO_DATE permits you to return a date expression corresponding to a Julian day count.
TO_CHAR permits you to return a Julian day count corresponding to a date expression, as shown in the following example:
SELECT
TO_CHAR('1776-07-04','J') AS JulianCount,
TO_DATE(2369916,'J') AS JulianDate
Default Date Format Examples
The following embedded SQL example specifies date strings that are parsed using the default date format. Both of these are converted to the DATE data type internal value of 60537:
NEW SQLCODE
&sql(SELECT
TO_DATE('29 September 2018'),
TO_DATE('29 SEP 2018')
INTO :a,:b)
IF SQLCODE=0 {WRITE a,!,b }
ELSE { WRITE "error:",SQLCODE }
The following embedded SQL example specifies date strings with two-digit years with
format default. Note that two-digit years default to 1900 through 1999. Thus, the internal DATE value is 24012:
NEW SQLCODE
&sql(SELECT
TO_DATE('29 September 06'),
TO_DATE('29 SEP 06')
INTO :a,:b)
IF SQLCODE=0 {WRITE a,!,b }
ELSE { WRITE "error:",SQLCODE }
Specified Date Format Examples
The following embedded SQL example specifies date strings in various formats. All of these are converted to the DATE data type internal value of 64701.
NEW SQLCODE
&sql(SELECT
TO_DATE('2018 Feb 22','YYYY MON DD'),
TO_DATE('FEBRUARY 22, 2018','month dd, YYYY'),
TO_DATE('2018***02***22','YYYY***MM***DD'),
TO_DATE('02/22/2018','MM/DD/YYYY')
INTO :a,:b,:c,:d)
IF SQLCODE=0 {WRITE !,a,!,b,!,c,!,d }
ELSE { WRITE "error:",SQLCODE }
The following embedded SQL example specifies date formats that do not require element separators. They return the date internal value of 64701:
NEW SQLCODE
&sql(SELECT
TO_DATE('02222018','MMDDYYYY'),
TO_DATE('22022018','DDMMYYYY'),
TO_DATE('20182202','YYYYDDMM'),
TO_DATE('20180222','YYYYMMDD')
INTO :a,:b,:c,:d)
IF SQLCODE=0 {WRITE !,a,!,b,!,c,!,d }
ELSE { WRITE "error:",SQLCODE }
The following example specifies the YYYYMM date format. It does not require element separators. It supplies 01 for the missing day element, returning the date 64800 (June 1, 2018):
NEW SQLCODE
&sql(SELECT TO_DATE('201806','YYYYMM')
INTO :a )
IF SQLCODE=0 {WRITE a," = ",$ZDATE(a,1,,4) }
ELSE { WRITE "error:",SQLCODE }