From derby-dev-return-84325-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Tue Feb 01 05:19:22 2011 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 69281 invoked from network); 1 Feb 2011 05:19:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Feb 2011 05:19:22 -0000 Received: (qmail 2353 invoked by uid 500); 1 Feb 2011 05:19:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 2244 invoked by uid 500); 1 Feb 2011 05:19:20 -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 2230 invoked by uid 99); 1 Feb 2011 05:19:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 05:19:19 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 05:19:19 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E97131835F0 for ; Tue, 1 Feb 2011 05:18:28 +0000 (UTC) Date: Tue, 1 Feb 2011 05:18:28 +0000 (UTC) From: "C.S. Nirmal J. Fernando (JIRA)" To: derby-dev@db.apache.org Message-ID: <168911822.1511.1296537508937.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] Resolved: (DERBY-4625) TIMESTAMP function doesn't accept nanoseconds 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:all-tabpanel ] C.S. Nirmal J. Fernando resolved DERBY-4625. -------------------------------------------- Resolution: Fixed Issue & fix info: (was: [Repro attached]) Resolving this issue! > 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 > Fix For: 10.7.1.1 > > 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira