Re: PreparedStatement.setDate() behavior with OVERLAPS

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher BROWN <brown(at)reflexe(dot)fr>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: PreparedStatement.setDate() behavior with OVERLAPS
Date: 2015-08-11 17:22:36
Message-ID: CAB=Je-Hh70uWEVzznyjPQNYRnTsnYCYn6KW1CY_7p6KDGPB-Aw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dave,

This exact pull request introduces notion of TZ and non-TZ classes in
jdbc driver: https://github.com/pgjdbc/pgjdbc/pull/340

Well, the PR needs some cleanup, however it allows to bind variables
and tell server we are binding TZ. I think it would solve the issue.

Another approach is to support java8's java.time APIs, however I think
it is more like a long-term solution.

Vladimir

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Steffen Heil (Mailinglisten) 2015-08-15 17:16:11 Patch fo select ip and/or port for outgoing connections
Previous Message Dave Cramer 2015-08-11 15:03:09 Re: PreparedStatement.setDate() behavior with OVERLAPS