On Tue, 10 Mar 2020 11:34:40 +0100
Dimitry Sibiryakov wrote:
> 10.03.2020 09:48, Alex Peshkoff via Firebird-devel wrote:
> > May be for old windows versions - yes, some problems. All the others
> > upgrade ICU as a part > of regular OS upgrade. I.e. if one already has
> > local ICU extended forma
On 2020-03-09 16:12, Adriano dos Santos Fernandes wrote:
On 08/03/2020 06:24, Mark Rotteveel wrote:
Please enlighten me in what way will I have "misunderstood the thing
completely", and will "Jaybird users [..] have a very wrong behavior
forever"?
That I talked in almost every message here
On 2020-03-09 17:48, Tony Whyman wrote:
My reading is that when the server's ICU is used, TIMESTAMP/TIME with
TIME ZONE values are returned as UTC with both the time zone id and
the time zone offset as computed by the server's ICU taking into
account any daylight savings time variations.
I pres
On 2020-03-09 16:04, Adriano dos Santos Fernandes wrote:
On 08/03/2020 06:24, Mark Rotteveel wrote:
On 05-03-2020 17:14, Adriano dos Santos Fernandes wrote:
The JDBC specification doesn't support named time zones, only offset
time zones
(OffsetDateTime/OffsetTime),
Please point me to that
10.03.2020 09:48, Alex Peshkoff via Firebird-devel wrote:
May be for old windows versions - yes, some problems. All the others upgrade ICU as a part
of regular OS upgrade. I.e. if one already has local ICU extended format is definitely
useless overhead.
ICU appeared only in recent builds of
Tony (& others),
On 2020-03-09 19:48, Tony Whyman wrote:
The question then arises as to why this is not the normal way of
working? Using the client's local ICU introduces a maintenance headache.
This argument I personally hardly accept. May be for old windows
versions - yes, some problems.
