Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 23215 invoked from network); 11 Oct 2006 08:45:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Oct 2006 08:45:08 -0000 Received: (qmail 29410 invoked by uid 500); 11 Oct 2006 08:45:03 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 29382 invoked by uid 500); 11 Oct 2006 08:45:03 -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 29372 invoked by uid 99); 11 Oct 2006 08:45:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 01:45:03 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 01:45:02 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6F7E67142E2 for ; Wed, 11 Oct 2006 01:44:22 -0700 (PDT) Message-ID: <31209632.1160556262454.JavaMail.root@brutus> Date: Wed, 11 Oct 2006 01:44:22 -0700 (PDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1811) Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be incorrect. In-Reply-To: <16559744.1157260402366.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-1811?page=comments#action_12441379 ] Kristian Waagan commented on DERBY-1811: ---------------------------------------- Has all work been finsihed on this issue? If so, please close it. I was looking at this because we now see failures in the All suite for TimeHandlingTest under DerbyNetClient. > Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be incorrect. > ------------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-1811 > URL: http://issues.apache.org/jira/browse/DERBY-1811 > Project: Derby > Issue Type: Bug > Components: JDBC > Affects Versions: 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.3.2, 10.1.4.0, 10.2.1.6, 10.3.0.0 > Reporter: Daniel John Debrunner > Assigned To: Daniel John Debrunner > Fix For: 10.3.0.0 > > Attachments: derby1811_diff.txt > > > The date portion of the java.sql.Timestamp from a TIME column is intended to be the current date but instead can be any date value, based upon the last getXXX call that required a Java Calendar object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira