Re: Regression: Problems with Timestamp arguments

From: Vitalii Tymchyshyn <vit(at)tym(dot)im>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Lachezar Dobrev <l(dot)dobrev(at)gmail(dot)com>, PG-JDBC Mailing List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Regression: Problems with Timestamp arguments
Date: 2013-09-11 06:03:09
Message-ID: CABWW-d3zq-Y3nkd3ra27mcaaeYPoF6OqjtUdBZf26qcTBGbBPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Why so? I thought if driver will pass timestamp with tz some queries won't
work because of lack of implicit conversion, but I don't understand how can
it corrupt anything.
11 вер. 2013 01:37, "Kris Jurka" <books(at)ejurka(dot)com> напис.

>
>
> 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
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Thomas Kellerer 2013-09-11 06:22:37 Re: 9.3 and extended constraint error information
Previous Message Kris Jurka 2013-09-10 22:40:52 Re: 9.3 and extended constraint error information