[
https://issues.apache.org/jira/browse/DERBY-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880409#comment-13880409
]
Kim Haase edited comment on DERBY-6458 at 1/23/14 10:07 PM:
------------------------------------------------------------
Attaching DERBY-6458.diff and rrefsqlj27620.html, adding a clarifying sentence
to
M src/ref/rrefsqlj27620.dita
I hope this is sufficient.
was (Author: chaase3):
Attaching DERBY-6458.diff and rrefsqlj27620.html, adding a clarifying sentence
to
M src/ref/rrefsqlj27620.dita
I hope this is sufficent.
> The Reference Manual should state that the year, month, and day components of
> a timestamp must be positive integers.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6458
> URL: https://issues.apache.org/jira/browse/DERBY-6458
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-6458.diff, rrefsqlj27620.html
>
>
> There is no year 0, month 0, or day 0 in the notation scheme used by Derby
> timestamps. We should state this in the Reference Guide section titled
> "TIMESTAMP data type". The following script shows this:
> {noformat}
> connect 'jdbc:derby:memory:db;create=true';
> create table t( a timestamp );
> -- fails because year, month, and day must be positive integers
> insert into t values ( '0000-00-00 00:00:00' );
> insert into t values ( '0001-00-00 00:00:00' );
> insert into t values ( '0001-01-00 00:00:00' );
> -- succeeds
> insert into t values ( '0001-01-01 00:00:00' );
> select * from t;
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
