Re: ResultSet.getObject(..., LocalTime.class) not working with Postgres timetz type

From: Philippe Marschall <pm(at)netcetera(dot)ch>
To: pgsql-jdbc(at)lists(dot)postgresql(dot)org
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, Mark Rotteveel <mark(at)lawinegevaar(dot)nl>
Subject: Re: ResultSet.getObject(..., LocalTime.class) not working with Postgres timetz type
Date: 2019-04-17 12:03:39
Message-ID: 49e99d98-679e-ab0c-92e5-15fff9e63257@netcetera.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On 16.04.19 02:20, Dave Cramer wrote:
>
>
> The whole time, timestamp, timezone thing was not well thought out and
> is the bane of all driver implementers existence...

Pre JDBC 4.2 and java.sql types I agree.

JDBC 4.2+ and java.time types I disagree. Issues with JDBC 4.2+ and
java.time types start when:

- people want backwards compatibility with bugs in java.sql
- support is implemented in terms of java.sql
- people want to support other java.time types besides the direct 1:1
mappings

If you stay away from these then everything is really easy.

Cheers
Philippe

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Philippe Marschall 2019-04-17 12:35:30 Re: ResultSet.getObject(..., LocalTime.class) not working with Postgres timetz type
Previous Message Philippe Marschall 2019-04-17 12:00:25 Re: ResultSet.getObject(..., LocalTime.class) not working with Postgres timetz type