Re: Timestamp Conversion Woes Redux - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Timestamp Conversion Woes Redux
Date
Msg-id D8B5F558-983C-4831-AA41-CD063B0CA341@fastcrypt.com
Whole thread Raw
In response to Re: Timestamp Conversion Woes Redux  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
Yes, it does, and yes they should be.

The real solution appears to be to use the current server timezone,
not the
other way around. See my other posts.

Dave
On 20-Jul-05, at 1:41 PM, Tom Lane wrote:

> Kris Jurka <books@ejurka.com> writes:
>
>> ... Problems arise when the server and JDK don't have the
>> same set of timezones, which will happen, but not often.  We could
>> easily
>> add a URL parameter to bail people out of here though.
>>
>
> Hmm ... does Java have a standard set of timezone names?  If so,
> does it
> bear any resemblance to the zic database names?
>
>             regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
>
>


pgsql-jdbc by date:

Previous
From: Christian Cryder
Date:
Subject: Re: Timestamp Conversion Woes Redux
Next
From: Vadim Nasardinov
Date:
Subject: Java's set of timezone names (was: Re: Timestamp Conversion Woes Redux)