| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Lachezar Dobrev <l(dot)dobrev(at)gmail(dot)com> |
| Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Regression: Problems with Timestamp arguments |
| Date: | 2013-09-10 22:37:04 |
| Message-ID: | alpine.BSO.2.03.1309101834110.15199@ejurka.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, 10 Sep 2013, Lachezar Dobrev wrote:
> I've made a blunt stab at working around the issue.
> The attached patch adds a new parameter to the JDBC URL: timestamp.
> The parameter can be wither 'with_timezone' or 'without_timezone'. If
> the parameter is missing, or has a different value then the current
> behaviour (using Oid.UNSPECIFIED) is exhibited. With the parameters
> specified correctly one of the Oid.TIMESTAMP or Oid.TIMESTAMPTZ is
> used when sending Timestamp arguments to the server.
This won't really work in general though. If you have a database that has
both timestamp and timestamptz fields in it, there is no valid setting of
this configuration option. Setting it either way will result in silent
corruption of your data.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2013-09-10 22:40:52 | Re: 9.3 and extended constraint error information |
| Previous Message | Thomas Kellerer | 2013-09-10 22:04:44 | 9.3 and extended constraint error information |