On 8-7-2019 22:01, Vlad Khorsun wrote:
06.07.2019 12:16, Mark Rotteveel wrote:
Should we reconsider current implementation ?
I speak about seconds in Java ZoneOffset type. How do you going to store
in Firebird database timestamps like '01.01.2020 12:34:56 +07:08:09' ?
I will repeat what I said in my previous reply:
"""
Unless someone comes up with a complete proposal for discussion (and not
an email thread with dozens of conflicting opinions), then I suggest we
keep the implementation as is.
I'll repeat my position:
1. The minimal thing that can and should be done to address the problem
that kicked off this email thread, is to ensure that `decodeTimestampTz`
has a fallback if ICU is not available to render named zones properly
(that is: render the time as UTC or +00:00 which is 1) possible with the
current information available and 2) an acceptable fallback).
2. Changing how WITH TIME ZONE types fundamentally work in the protocol
this late in the development cycle is in my opinion problematic, and the
alternatives suggested up to this point are - in my opinion - not better
and in some cases worse.
"""
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
