Re: Timestamp Conversion Woes Redux

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kris Jurka <books(at)ejurka(dot)com>, Oliver Jowett <oliver(at)opencloud(dot)com>, Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Timestamp Conversion Woes Redux
Date: 2005-07-20 17:50:31
Message-ID: D8B5F558-983C-4831-AA41-CD063B0CA341@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)ejurka(dot)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
>
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2005-07-20 18:13:25 Re: Timestamp Conversion Woes Redux
Previous Message Christian Cryder 2005-07-20 17:47:04 Re: Timestamp Conversion Woes Redux