You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/05/03 21:54:15 UTC
[jira] Updated: (DERBY-2602) TIMESTAMP value is truncated when
return to client
[ https://issues.apache.org/jira/browse/DERBY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-2602:
----------------------------------
Attachment: d2602.java
The issue is with java.sql.Timestamp object as well
Attached is a reproduction which shows the following behavior.
Embedded Timestamp
getHours:17
getMinutes:14
getSeconds:24
getNanos:97625551
Network Timestamp
getHours:17
getMinutes:14
getSeconds:24
getNanos:97625000
> 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.0.0
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: d2602.java
>
>
> 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.