Re: Timestamp Conversion Woes Redux

Dave Cramer wrote:

> In order to calculate the milliseconds the driver takes into account
> the time zone, information the DBMS may or may not store. If no
> Calendar object is supplied the driver will use the default Calendar
> whose time zone is that of the JVM that is
> running the application. If the DBMS does provide timezone  information
> the driver will simply use that and IGNORE (my caps) a  Calendar object
> that may have been passed to it.

Not having read the source material, but isn't this talking about the
getTimestamp() path not the setTimestamp() path?

-O