Re: Literal vs parameterized 'timestamp with time zone' value

From: Christopher Hunt <huntc(at)internode(dot)on(dot)net>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Literal vs parameterized 'timestamp with time zone' value
Date: 2007-06-18 13:58:53
Message-ID: EE8A7058-2133-4FC0-9C12-D23ECB4708C6@internode.on.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Thanks!

On 18/06/2007, at 11:33 PM, Dave Cramer wrote:

> Christopher,
>
> Use a more recent jar. There is a problem with the spec, and
> postgresql. The spec does not have two different timestamps. In
> previous versions we bound the type to timestamp without timezone.
> In more recent versions we bind it to 'unknown' which allows the
> server to decide.
>
> If this fails then appending ?protocolVersion=2 will work, however
> you won't be server side prepared statements.

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Javier Caballero 2007-06-19 11:05:31 Driver modified for JDeveloper+ADF communication
Previous Message Dave Cramer 2007-06-18 13:33:44 Re: Literal vs parameterized 'timestamp with time zone' value