Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 78532 invoked from network); 19 Sep 2006 20:49:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Sep 2006 20:49:01 -0000 Received: (qmail 42752 invoked by uid 500); 19 Sep 2006 20:49:00 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 42722 invoked by uid 500); 19 Sep 2006 20:49:00 -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 42712 invoked by uid 99); 19 Sep 2006 20:49:00 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2006 13:49:00 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from ([209.237.227.198:35204] helo=brutus.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id A0/1B-28275-AB750154 for ; Tue, 19 Sep 2006 13:48:58 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D43E7410069 for ; Tue, 19 Sep 2006 20:45:22 +0000 (GMT) Message-ID: <5219135.1158698722855.JavaMail.jira@brutus> Date: Tue, 19 Sep 2006 13:45:22 -0700 (PDT) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-163) Timestamp formatting In-Reply-To: <1206356691.1109968127066.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-163?page=comments#action_12436000 ] Daniel John Debrunner commented on DERBY-163: --------------------------------------------- Derby's TIMESTAMP precision is nano-seconds, so the string format of that should support the complete resolution. > Timestamp formatting > -------------------- > > Key: DERBY-163 > URL: http://issues.apache.org/jira/browse/DERBY-163 > Project: Derby > Issue Type: Bug > Components: SQL, Newcomer > Affects Versions: 10.0.2.0 > Environment: Windows XP Professional SP1 > Reporter: George Baklarz > Priority: Minor > > The timestamp format within Derby contains the following information: > yyyy-mm-dd-hh.mm.ss.mmmmmm > When issuing a CURRENT TIMESTAMP function, it returns > yyyy-mm-dd-hh.mm.ss.mmm > If you do a TIMESTAMP('1988-12-15-17.12.30.123400') it will return > 1988-12-15-17.12.30.1234 > Is there any particular reason why Derby does not display the zeros at the end of the field? This may just be just to be consistent with the ISO standards, but if you look at the example in the manual, it shows: > VALUES TIMESTAMP(START_DATE, END_DATE) > 1988-12-25-17.12.30.000000 > If I try this with a simple table: > CREATE TABLE TS (A DATE, B TIME); > INSERT INTO TS VALUES (CURRENT DATE, CURRENT TIME); > SELECT TIMESTAMP(A,B) FROM TS; > ij> select timestamp(a,b) from ts; > 1 > -------------------------- > 2005-03-04 15:13:19.0 > So the 0's are not displayed, except for the first microsecond. The format needs to be clarified either in the manuals or corrected in the program. -- 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