Re: work in progress: timestamp patch

Dave Cramer wrote:

> One of the times he is trying to stick in the db is a non-existant  time
> if it is associated with a
> time zone
>
> stmt.execute("INSERT INTO Foo (t1) VALUES ('2005-04-03 02:29:43.0')");
>
> in any US timezone this time does not exist. In US/Mountain timezone  this
> inserts as  2005-04-03 03:29:43.0' note the hour has incremented from  2
> to 3

What's the underlying column, timestamp or timestamptz?

How is the value represented on the Java side? Seems like if you used
Timestamp + a UTC calendar on both the set and get paths, it should work
fine with no need to mess with the server timezone (assuming untyped
parameters)?

-O