[
https://issues.apache.org/jira/browse/DERBY-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889928#action_12889928
]
Mamta A. Satoor commented on DERBY-4615:
----------------------------------------
Can't backport DERBY-2602 into 10.5 because it will change the behavior of
client server product when we already have branches on top of the 10.5
codeline. Because of that, I had to change the test to not look for nanosec
granularity after the merge of DERBY-4615 into 10.5 codeline. The changes for
DERBY-4615 are now in 10.5 codeline
> 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
> Fix For: 10.5.3.1, 10.6.1.0
>
> 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.
-
You can reply to this email to add a comment to the issue online.
