[
https://issues.apache.org/jira/browse/DERBY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887504#action_12887504
]
Knut Anders Hatlen commented on DERBY-2602:
-------------------------------------------
Hi Mamta,
Before you backport the fix, please check that a client running head of 10.5
still can send and receive timestamps when talking to a 10.6.1.0 server, and
vice versa. I suspect that this scenario will break if the fix is backported
with no other changes.
> TIMESTAMP value is truncated when return to client
> ---------------------------------------------------
>
> Key: DERBY-2602
> URL: https://issues.apache.org/jira/browse/DERBY-2602
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.3.1.4
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
> Priority: Minor
> Fix For: 10.6.1.0
>
> Attachments: d2602.java, derby-2602-01-ad-dontTruncate.diff,
> derby-2602-01-ae-dontTruncate.diff, derby-2602-01-af-dontTruncate.diff
>
>
> In ParameterMappingTest I see the following differences between embedded
> and client. Client is truncating the TIMESTAMP value. Look for this bug
> number in the test for reproduction.
> case java.sql.Types.TIMESTAMP:
> if (param == 2)
> if (usingEmbedded())
> assertEquals("2004-03-12 21:14:24.938222433",
> val.toString());
> else
> assertEquals("2004-03-12 21:14:24.938222",
> val.toString());
> else if (param == 3)
> if (usingEmbedded())
> assertEquals("2004-04-12 04:25:26.462983731",
> val.toString());
> else
> assertEquals("2004-04-12 04:25:26.462983",
> val.toString());
> break;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
