From derby-dev-return-92957-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Thu Feb 2 14:40:15 2012 Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 74C9F9B8E for ; Thu, 2 Feb 2012 14:40:15 +0000 (UTC) Received: (qmail 87305 invoked by uid 500); 2 Feb 2012 14:40:15 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 87264 invoked by uid 500); 2 Feb 2012 14:40:14 -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 87257 invoked by uid 99); 2 Feb 2012 14:40:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 14:40:14 +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; Thu, 02 Feb 2012 14:40:13 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 51AAE1889FE for ; Thu, 2 Feb 2012 14:39:53 +0000 (UTC) Date: Thu, 2 Feb 2012 14:39:53 +0000 (UTC) From: "Kim Haase (Assigned) (JIRA)" To: derby-dev@db.apache.org Message-ID: <1007208574.2823.1328193593335.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <549552620.1232.1328153874848.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Assigned] (DERBY-5596) TIMESTAMP doc gives wrong precision limitation 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-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase reassigned DERBY-5596: -------------------------------- Assignee: Kim Haase > TIMESTAMP doc gives wrong precision limitation > ---------------------------------------------- > > Key: DERBY-5596 > URL: https://issues.apache.org/jira/browse/DERBY-5596 > Project: Derby > Issue Type: Bug > Components: Documentation > Reporter: Dag H. Wanvik > Assignee: Kim Haase > > Derby accepts nanosecond fractions. e,g. > create table t(i timestamp); > insert into t values TIMESTAMP('1962-09-23 03:23:34.123456789'); > but the refman doc states: > > Derby supports the following formats for TIMESTAMP: > > > > yyyy-mm-dd hh:mm:ss[.nnnnnn] > > yyyy-mm-dd-hh.mm.ss[.nnnnnn] > > > > The first of the two formats above is the java.sql.Timestamp format. > > > >The year must always have four digits. Months, days, and hours may have one or two digits. Minutes and seconds must have two digits. > >Nanoseconds, if present, may have between one and six digits. > Nine digits are accepted, not six: > select * from t; > I > ----------------------------- > 1962-09-23 03:23:34.123456789 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira