On 23/04/2019 19:10, Adriano dos Santos Fernandes wrote:
Regarding the exception, what would happen if you store valid date at
that time and you later, with new DST rules, try to read it?
That is not a problem. The ambiguity exists only when transforming a
timestamp+TZ (as one sees it) to UTC. After parse the literal, it's
always in UTC+TZ.
UTC+TZ is always transformed to a valid displayable timestamp+TZ.
But whether it is the RIGHT transformation is any bodies guess!
We still need a properly managed solution to handing local time
normalization, and since even the TZ database does not provide that much
of it is always going to be guesswork. :(
The SAFE option for handling normalized times is to record the location
rather than some arbitrary timezone. The second one selects a timezone
one ALSO needs to record the version of timezone data used with it ...
timestamp+TZ is simply not the solution for most cases - current day or
historic ... and the further restrictions FB4 introduces just makes
matters worse!
--
Lester Caine - G8HFL
-----------------------------
Contact - https://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - https://lsces.co.uk
EnquirySolve - https://enquirysolve.com/
Model Engineers Digital Workshop - https://medw.co.uk
Rainbow Digital Media - https://rainbowdigitalmedia.co.uk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
