Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49364 invoked from network); 13 Apr 2010 19:23:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Apr 2010 19:23:24 -0000 Received: (qmail 49145 invoked by uid 500); 13 Apr 2010 19:23:24 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 49118 invoked by uid 500); 13 Apr 2010 19:23:23 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 49111 invoked by uid 99); 13 Apr 2010 19:23:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 19:23:23 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 19:23:21 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3DJMxdx001431 for ; Tue, 13 Apr 2010 15:22:59 -0400 (EDT) Message-ID: <22256164.65671271186579601.JavaMail.jira@thor> Date: Tue, 13 Apr 2010 15:22:59 -0400 (EDT) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-2602) TIMESTAMP value is truncated when return to client In-Reply-To: <17010421.1178134635553.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-2602. ---------------------------------- Resolution: Fixed I believe that this bug is fixed. I opened a related issue, DERBY-4614, to address bad JDBC metadata for timestamps, discovered while fixing this bug. > 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