Hi Christopher,
> If I haven't made any mistakes, this is what I get so far when looking
> at the driver's code:
Thanks for your analysis! You're probably right about it. As I
mentioned in that Stack Overflow question, all JDBC drivers behave the
same way (except for the SQLite one). So I guess the reason for this
is hidden in the somewhat controversial JDBC specs.
> Note that in our application, we do the following at the start but it
> looks a lot like a work around:
> TimeZone.setDefault(TimeZone.getTimeZone("GMT"));
That is a brute, yet effective workaround for many problems :-)
Cheers
Lukas
