Re: ABSTRACT: Please refer to following table concerning impacts of the leap second change in 2016. -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: ABSTRACT: Please refer to following table concerning impacts of the leap second change in 2016.
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Tue, 15 Nov 2016 10:08:09 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 10/19/2016 7:24 AM, Rob Berendt wrote:

[Regarding storing a timestamp containing a leap second]

What happened when you opened that PMR?

The DB2 team had a serious discussion about this and came to the
decision that without a specific example of an application that will
generate a leap second, DB2 will remain as-is: TIMESTAMP will NOT
support a leap second.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.