db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5596) TIMESTAMP doc gives wrong precision limitation
Date Thu, 02 Feb 2012 03:37:54 GMT
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

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;
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


View raw message