On Fri, 17 Dec 2004, John R Pierce wrote:
> > The really serious problem with this is the assumption that the server
> > has the same set of available timezones (and spellings of same) as the
> > client does.
> timezones seriously suck.
> China uses CST. So does North America. How you gonna resolve THAT ?
Java (and pg) timezones aren't just abbreviations. Mine is
"America/Los_Angeles" which is pretty unique.
> The proper solution is to use "ISO" time with -07 / +08 kinda timezones
> if you need to get data in/out of timestampz fields.... Java can do
> this just by specifying the right option when you convert a calendar
> time to a string.
When sending timestamp information to/from the database this is indeed
what is used, but this thread is about resolving the fact that Java's
concept of timestamp is halfway between with timezone and without timezone
which is tough to match up with pg and the sql standard.
In response to
pgsql-jdbc by date
|Next:||From: Xavier Poinsard||Date: 2004-12-18 13:53:55|
|Subject: Re: Patch to reduce the number of messages to translate|
|Previous:||From: John R Pierce||Date: 2004-12-18 07:51:11|
|Subject: Re: Bug in JDBC-Driver?|