db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4615) EmbedCallableStatement ignores Calendar in getDate, getTime and getTimestamp
Date Mon, 12 Jul 2010 14:36:53 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887384#action_12887384
] 

Mamta A. Satoor commented on DERBY-4615:
----------------------------------------

DERBY-2602 is not in the list of bugs identified for backport to 10.5 but I can look into
backporting it so DERBY-4615 does not have the above failure after the merge. Please let me
know if any one has any objection to backport of DERBY-2602.

> 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: Mamta A. Satoor
>             Fix For: 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.


Mime
View raw message