[tz] DST ends 2040 in Oracle database

Robert Elz kre at munnari.OZ.AU
Tue Jan 29 06:43:17 UTC 2019

    Date:        Tue, 29 Jan 2019 12:13:47 +0800
    From:        Phake Nick <c933103 at gmail.com>
    Message-ID:  <CAGHjPPL=8HkNyvdHAqJRAd48Dso37n11sx_5DP1Aygxs70A7Rg at mail.gmail.com>

  | Except it is already year 2019 and 2038 January 19 is now only less than 19
  | years into the future. If one get a 20-year mortgage now, the final payment
  | day/time will already be after 2038. It's probably about time for
  | developers and vendors to consider the problem more seriously.

Perhaps, but if you haven't already done so, you need to read Paul's

The developers who need to take this kind of issue seriously are the ones
(to use your example) who are recoding the mortgage end date/time.

If your mortgage were in New York (probably a huge one, and 20 years
might not be enough...) then the end date time of that 20 year mortgage
should be recorded as "5:00 p.m. on the January 29, 2039, in
New York City".

If your mortgage is in Hong Kong (might need to be even longer than for
New York!) the end date time should be recorded as "17:00 on 29th of
January, 2039, in Hong Kong".

In each case the place might need to be more specific (that is the final
payment might need to be in a specific room in a specific building or
something, fo facilitate the document echange, or perhaps "at a location
to be agreed", but that isn't relevant to this discussion.)

Under no circumstances (other than specific agreement by the parties)
should it be recorded as "2039-01-29 21:00:00 UTC" or
"2030-01-29 09:00:00 UTC" (if I did the conversions in my head
correctly) - that would always be wrong (again unless that's
what was specifically agreed - the person/software recording the
end time should *never* make that kind of change "just because
UTC is always better".


More information about the tz mailing list