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

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.

Dave
On 18-Jun-07, at 8:59 AM, Christopher Hunt wrote:

> Thanks for responding.
>
> Alas, I have tried setTimestamp - in fact I started with that and
> ended up with a similar problem i.e. no rows returned with
> setTimestamp. I think that my problem is something else.
>
> The client and server processes are on the same machine.
>
> Any more ideas?
>
> Cheers,
> -C
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org