setTimestamp Time Zone Ignored in ServerPreparedStatement
Posted by: Benjamin Labonte
Date: October 17, 2014 01:05AM

As mentioned in there have been several bugs concerning time zones which should be fixed using the new code by setting useLegacyDatetimeCode=false.

One of the issues that has been fixed for the PreparedStatement is that now the time zone of the Calendar specified by the setTimestamp(int parameterIndex, java.sql.Timestamp x, Calendar cal) call is used to format the given Timestamp.

Why is this not the case for the ServerPreparedStatement?
The corresponding method setTimestampInternal(int parameterIndex, java.sql.Timestamp x, Calendar targetCalendar, TimeZone tz, boolean rollForward) simply ignores the given time zone tz if the legacy code is switched off.

Is this a bug?

Options: ReplyQuote

Written By
setTimestamp Time Zone Ignored in ServerPreparedStatement
October 17, 2014 01:05AM

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.