Re: ResultSet.getTimestamp(Calendar) off by one-hour
От | Roland Roberts |
---|---|
Тема | Re: ResultSet.getTimestamp(Calendar) off by one-hour |
Дата | |
Msg-id | 49BABEA4.60104@astrofoto.org обсуждение исходный текст |
Ответ на | Re: ResultSet.getTimestamp(Calendar) off by one-hour (Roland Roberts <roland@astrofoto.org>) |
Ответы |
Re: ResultSet.getTimestamp(Calendar) off by one-hour
|
Список | 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@rlenter.com 6818 Madeline Court roland@astrofoto.org Brooklyn, NY 11220
В списке pgsql-jdbc по дате отправления: