[ https://issues.apache.org/jira/browse/DERBY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2602:
---------------------------------
Attachment: derby-2602-01-af-dontTruncate.diff
Thanks, Knut. You are right. The abstract method in Connection makes this better. I have made
that change and added a compatibility test to the next rev of the patch: derby-2602-01-af-dontTruncate.diff.
I am re-running the regression tests now. Thanks.
> 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: Rick Hillegas
> Priority: Minor
> 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.
-
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
|