Re: TimeZone conversion in Connector/J; maybe a patch is in order?
Posted by: David Tonhofer
Date: October 07, 2004 04:29PM

Hi Mark,

You are talking about

ResultSet.getDate(int columnIndex,Calendar cal)

and sundry right? I can't use that - access is buried down in the Jakarta DynaBeans, I just
get a "Timestamp" in the end, configured according to what the Connector thinks
its conversion Calendar and Timezone currently are.

As I wanted to have some possibility to *easily* and *globally* make the Connector use the
Timezone I want I ended up with Connector/J code that uses the additional 'conversionCalendar'
in the Connection URL, as described in the previous postings. As a bonus, Timezone conversion
code was made clearer, at the cost of slight increase of complexity of the setup procedure.

I don't know if you are prepared to spend some mind-share on the changes I have made, might be
of interest. Or has this all been changed in 3.1.4 anyway?


-- David

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.