POSIX TIME CONVERTER SOFTWARE
POSIX TIME CONVERTER CODE

Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose.

POSIX TIME CONVERTER CODE

The sample code is provided on an 'AS IS' basis.

POSIX TIME CONVERTER SOFTWARE

Progress Software Corporation makes no explicit or implied claims to the validity of this information.Īny sample code provided on this site is not supported under any Progress support program or service.

However, the information provided is for your information only. Progress Software Corporation makes all reasonable efforts to verify this information. The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). * following variable holds epoch time value (in milliseconds) */ĭEFINE VARIABLE vEpochTimeValue AS INT64 NO-UNDO INITIAL 1325635327000.ĪSSIGN vDateOrDateTimeTZ = ADD-INTERVAL(vDateOrDateTimeTZ,vEpochTimeValue,'MILLISECONDS'). These time values can also easily be converted into ABL DATETIME-TZ values using the following code:ĭEFINE VARIABLE vDateOrDateTimeTZ AS DATETIME-TZ NO-UNDO INITIAL. * display value to show it conforms to epoch base value (useful for datetime) */ĪSSIGN vDateOrDateTime = ADD-INTERVAL(vDateOrDateTime,vEpochTimeValue,'SECONDS'). * following variable holds epoch time value (in seconds) */ĭEFINE VARIABLE vEpochTimeValue AS INTEGER NO-UNDO INITIAL 1325635327. * following variable is initialized to base unix epoch time value */ĭEFINE VARIABLE vDateOrDateTime AS DATETIME NO-UNDO INITIAL. These time values can easily be converted into ABL DATE or DATETIME values using the following code: Here, we used the LEFT() function to return just the first ten digits, as well as the CONVERT() function to return an integer.Unix Epoch time values are a mechanism for describing instants in time, defined as the number of seconds elapsed since midnight (UTC) of January 1, 1970. SELECT DATEADD(s, CONVERT(int, 10)), '') One option is to reduce the precision: DECLARE bigint = 1867914562715876900 We have a couple of options for dealing with this. This Unix timestamp contains nanosecond precision and has too many digits for an integer. That’s because the Unix timestamp value is larger than what an integer can hold. We could get an overflow error like this: Msg 8115, Level 16, State 2, Line 1Īrithmetic overflow error converting expression to data type int. When faced with a larger Unix timestamp value like the following: SELECT DATEADD(s, 1867914562715876900, '') Mind you, this is superfluous, because we could have just done the following: SELECT GETUTCDATE() Larger Unix Timestamps Here’s an example that uses the Unix timestamp based on the current date/time: SELECT DATEADD(s, DATEDIFF(s, '', GETUTCDATE()), '') In this case, the unix timestamp was 1860935119, which translated into a date and time of 14:25:19.000. Here’s an example of converting a Unix timestamp to a date/time value: SELECT DATEADD(s, 1860935119, '') The Unix timestamp (also known as Unix Epoch time, Unix time, or POSIX time) is the number of seconds that have elapsed since 00:00:00 Thursday, 1 January 1970, Coordinated Universal Time (UTC).

In SQL Server, we can use the following method to return a date and time based on a given Unix timestamp.

Posix time converter