You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/06 19:35:22 UTC
[jira] [Resolved] (DERBY-5596) TIMESTAMP doc gives wrong precision
limitation
[ https://issues.apache.org/jira/browse/DERBY-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-5596.
------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
Thanks, Rick! If no one's asked the question before, there's no need to answer it.
Committed patch DERBY-5596.diff to documentation trunk at revision 1310489.
> 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
> Fix For: 10.9.0.0
>
> 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