[
https://issues.apache.org/jira/browse/DERBY-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248417#comment-13248417
]
Rick Hillegas commented on DERBY-5596:
--------------------------------------
Hi Kim,
Thanks for making these changes. I don't know a handy name for the other
format. Documentation for the two formats goes back to 10.1. The formats don't
appear in the 10.0 reference guide. I think it's ok for the other format to not
have a handy name. +1 to these changes.
> 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
> Affects Versions: 10.8.2.2
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
> Attachments: DERBY-5596.diff, rrefsqlj27620.html
>
>
> 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;
> I
> -----------------------------
> 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
