On 03/06/2020 08:23, Lester Caine wrote:
On 02/06/2020 22:17, Dimitry Sibiryakov wrote:
02.06.2020 21:45, Mark Rotteveel wrote:
I think that is extremely confusing, and not acceptable.
That's why everyone was given several years to replace CURRENT_TIME
with LOCALTIME and don't use TIME WITH TIMEZONE at all.
Has
https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
Been replaced with something more up to date?
https://github.com/FirebirdSQL/firebird/blob/master/doc/sql.extensions/README.time_zone.md
should be a stable URL ?
Certainly I have no intention of doing anything other than retaining ALL
timestamps at UTC AND running the server local time as UTC. Displaying
and handling CLIENT local times is an interface problem and not
something which should be inconsistent in the core data ... especially
when one does not know what future time offsets will actually be ...
It would be nice to see the final paragraph much closer to the top so
that the fundamental problems of using the TZ database is highlighted
earlier. THAT is an explanation of where the FB4 approach to them may or
may not be appropriate. Also still missing is the lack of second
accuracy with timezone offsets in the FB4 version and that dates prior
to 1970 may produce different results. It should be clear exactly which
version of TZ data is bundled so we know if pre-19790 data is included
or not ...
--
Lester Caine - G8HFL
-----------------------------
Contact - https://lsces.uk/wiki/Contact
L.S.Caine Electronic Services - https://lsces.uk
Model Engineers Digital Workshop - https://medw.uk
Rainbow Digital Media - https://rainbowdigitalmedia.uk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
