[DERBY-163] Timestamps do not display trailing zeros

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.0.2.0
• Fix Version/s: 10.2.2.0
• Component/s: Documentation
• Labels: derby_triage10_5_2
• Environment: Windows XP Professional SP1
• Urgency: Normal
• Issue & fix info: Newcomer
• Assignee: Unassigned
• Reporter: George Baklarz
• Created: 05/Mar/05 05:19
• Updated: 03/Sep/14 08:31
• Resolved: 28/Dec/12 10:54

Description

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.

Issue Links

• is part of: DERBY-1839 Doc Review Updates - Ref Manual