On Friday 09 September 2005 07:18, Adrian Cox wrote:
> I couldn't find anything on this with Google, but I've got a 2ms
> offset between the java.sql.Timestamp representation and the string
> representation of a "timestamp with time zone".
>
> I've tried the following JDBC releases: 8.1dev-401 JDBC 3, 8.0-312
> JDBC 3, pg74.216.jdbc3.jar. The server is the Debian package

Since you're a Debian user, there is a greater-than-zero chance you
may be using a free java runtime like GCJ or some such. If so, it
would be helpful if you could also mention the version of GCJ that
you're using. In old versions of GNU Classpath, the implementation of
java.sql.Timestamp was buggy. (It's a little tricky to get right due
to the fact that the fractional seconds - the "nanos" - are separate
from whole seconds. Care must be taken when converting this slightly
schizophrenic internal representation to/from milliseconds.)

The only specific bug I remember is this one:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16574

There might have been others.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings