Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 89597 invoked from network); 21 Jan 2008 13:04:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2008 13:04:01 -0000 Received: (qmail 68904 invoked by uid 500); 21 Jan 2008 13:03:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 68877 invoked by uid 500); 21 Jan 2008 13:03:50 -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 68868 invoked by uid 99); 21 Jan 2008 13:03:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2008 05:03:50 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2008 13:03:45 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 972F071420D for ; Mon, 21 Jan 2008 05:03:37 -0800 (PST) Message-ID: <2142129.1200920617615.JavaMail.jira@brutus> Date: Mon, 21 Jan 2008 05:03:37 -0800 (PST) From: "Sandeep A (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Assigned: (DERBY-163) Timestamps do not display trailing zeros 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-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep A reassigned DERBY-163: ------------------------------- Assignee: Sandeep A > Timestamps do not display trailing zeros > ---------------------------------------- > > Key: DERBY-163 > URL: https://issues.apache.org/jira/browse/DERBY-163 > Project: Derby > Issue Type: Bug > Components: Newcomer, SQL > Affects Versions: 10.0.2.0 > Environment: Windows XP Professional SP1 > Reporter: George Baklarz > Assignee: Sandeep A > 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. - You can reply to this email to add a comment to the issue online.