Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 40140 invoked from network); 21 Sep 2010 14:25:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Sep 2010 14:25:58 -0000 Received: (qmail 4699 invoked by uid 500); 21 Sep 2010 14:25:58 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 4497 invoked by uid 500); 21 Sep 2010 14:25:55 -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 4490 invoked by uid 99); 21 Sep 2010 14:25:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Sep 2010 14:25:53 +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, 21 Sep 2010 14:25:53 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o8LEPWp4015736 for ; Tue, 21 Sep 2010 14:25:33 GMT Message-ID: <25822921.316771285079132905.JavaMail.jira@thor> Date: Tue, 21 Sep 2010 10:25:32 -0400 (EDT) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4625) TIMESTAMP function doesn't accept nanoseconds In-Reply-To: <32681535.112341271847531633.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913005#action_12913005 ] Knut Anders Hatlen commented on DERBY-4625: ------------------------------------------- Thanks, Nirmal! The patch looks good to me. The new test case in DateTimeTest was commented out. I've commented it back in and started the regression tests suites. I'll commit the fix if the tests pass. > TIMESTAMP function doesn't accept nanoseconds > --------------------------------------------- > > Key: DERBY-4625 > URL: https://issues.apache.org/jira/browse/DERBY-4625 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.5.3.0 > Reporter: Knut Anders Hatlen > Assignee: C.S. Nirmal J. Fernando > Priority: Minor > Attachments: derby-4625-1.diff, derby_4625-2.diff > > > The TIMESTAMP function fails if the string argument specifies the number of nanoseconds. It works if the argument is limited to microsecond resolution. > ij> values timestamp('2010-04-21 12:00:00.123456'); > 1 > -------------------------- > 2010-04-21 12:00:00.123456 > 1 row selected > ij> values timestamp('2010-04-21 12:00:00.123456789'); > ERROR 22008: '2010-04-21 12:00:00.123456789' is an invalid argument to the timestamp function. > Since Derby (and JDBC) supports nanosecond resolution, the TIMESTAMP function should also support it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.