Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database

From: stan(at)marencik(dot)cz
To: Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database
Date: 2019-10-16 10:52:30
Message-ID: 37961571223150@iva6-22e79380f52c.qloud-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

This was a bug created in https://www.postgresql.org/list/pgsql-jdbc/

I haven't an account on github so much easier for me will be to make a fork and fix myself...

Thank you,

Jan

16.10.2019, 06:20, "Michael Paquier" <michael(at)paquier(dot)xyz>:
> On Tue, Oct 15, 2019 at 06:52:12PM +0000, PG Bug reporting form wrote:
>>  Java DateOffsetTime value correctly stored to database to timestamptz. I see
>>  right conversion to string including right time zone.
>>  Opposite process doesn't get the right DateOffsetTime value from database.
>>  In my case the string representation stored to database is 2019-10-15
>>  20:26:41.391055+02 but I get 2019-10-15T18:26:41.391055Z which doesn't by +2
>>  hours which is my time zone.
>>  I think the bug is in TimestampUtils line 513:
>>      // Postgres is always UTC
>>      OffsetDateTime result = OffsetDateTime.of(ts.year, ts.month, ts.day,
>>  ts.hour, ts.minute, ts.second, ts.nanos, zoneOffset)
>>          .withOffsetSameInstant(ZoneOffset.UTC);
>>  The last line ".withOffsetSameInstant(ZoneOffset.UTC);" is the bug
>
> As an issue for the Postgres JDBC driver, I think that you should
> either contact pgsql-bugs:
> https://www.postgresql.org/list/pgsql-jdbc/
> Or raise an issue where the project is located:
> https://github.com/pgjdbc/pgjdbc
>
> Thanks,
> --
> Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2019-10-16 11:33:44 Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
Previous Message PG Bug reporting form 2019-10-16 08:50:43 BUG #16061: pgadmin