[ 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
