| From: | Michael Paquier <michael(at)paquier(dot)xyz> | 
|---|---|
| To: | stan(at)marencik(dot)cz, pgsql-bugs(at)lists(dot)postgresql(dot)org | 
| Subject: | Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database | 
| Date: | 2019-10-16 04:20:27 | 
| Message-ID: | 20191016042027.GC2602@paquier.xyz | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-bugs | 
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-10-16 04:41:12 | Re: BUG #16058: show session_user shows a not clear error message | 
| Previous Message | Maciek Sakrejda | 2019-10-15 21:11:43 | Duplicate Workers entries in some EXPLAIN plans |