[
https://issues.apache.org/jira/browse/DERBY-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4615:
--------------------------------------
Attachment: derby-4615-1a.diff
Currently, the problem is that EmbedCallableStatement defines
getXXX(int,Calendar) in terms of getXXX(int), so the Calendar argument is lost.
The attached patch turns this situation around. Now all the work is done in the
getters that take a Calendar argument, and the Calendar-less getters just
forward calls to them after adding the default Calendar instance to the
argument list.
Now the new test case in CallableTest runs cleanly both with the embedded
driver and the client driver. I've started a full regression test run.
> EmbedCallableStatement ignores Calendar in getDate, getTime and getTimestamp
> ----------------------------------------------------------------------------
>
> Key: DERBY-4615
> URL: https://issues.apache.org/jira/browse/DERBY-4615
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.5.3.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Attachments: derby-4615-1a.diff, test.diff
>
>
> The getDate(), getTime() and getTimestamp() methods in EmbedCallableStatement
> ignore the Calendar argument, and therefore give the wrong results if some
> other calendar than the default calendar is passed in. The client driver
> seems to do the right thing, though.
> Also note that none of these methods are ever called by any of the regression
> tests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
