From: | Roland Roberts <roland(at)astrofoto(dot)org> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: ResultSet.getTimestamp(Calendar) off by one-hour |
Date: | 2009-03-13 20:14:28 |
Message-ID: | 49BABEA4.60104@astrofoto.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Roland Roberts wrote:
> Okay, postgresql appears to be using the standard TZ offset regardless
> of whether or not DST is in effect on the day in question.
Hmmm, I *can* get the correct behavior IF I assign the environment
variable TZ=America/New_York before I run the client program. But I
don't need to do that when I'm talking to Oracle. For the Oracle case,
the database is on another host, both still in US/Eastern time zone.
Are there other ways to get PostgreSQL JDBC to understand the client
timezone w/o explicitly setting TZ? I'm trying to find an idiot-proof
(well, I'll settle for an idiot-resistant) method.
roland
--
PGP Key ID: 66 BC 3B CD
Roland B. Roberts, PhD RL Enterprises
roland(at)rlenter(dot)com 6818 Madeline Court
roland(at)astrofoto(dot)org Brooklyn, NY 11220
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-13 20:16:35 | Re: ResultSet.getTimestamp(Calendar) off by one-hour |
Previous Message | Roland Roberts | 2009-03-13 19:04:40 | Re: ResultSet.getTimestamp(Calendar) off by one-hour |