[ https://issues.apache.org/jira/browse/DERBY-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475602
]
Tomohito Nakayama commented on DERBY-908:
-----------------------------------------
I think next example in minutes page is for duration which is not supported.
http://db.apache.org/derby/docs/dev/ref/rrefminutefunc.html
>Select all classes that do not end on a full hour:
>
>SELECT * FROM table1 WHERE MINUTE(ending) < 60;
I think this should be corrected in this issue.
> YEAR,SECOND,MONTH, MINUTE, HOUR and DAY functions have incorrect information on durations.
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-908
> URL: https://issues.apache.org/jira/browse/DERBY-908
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assigned To: Bryan Pendleton
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: docChanges.diff, docChanges_v2.diff, docChanges_v3.diff, docChanges_v4.diff,
rrefdayfunc.html, rrefdayfunc.html, rrefdayfunc.html, rrefhourfunc.html, rrefhourfunc.html,
rrefhourfunc.html, rrefminutefunc.html, rrefminutefunc.html, rrefminutefunc.html, rrefmonthfunc.html,
rrefmonthfunc.html, rrefmonthfunc.html, rrefsecondfunc.html, rrefsecondfunc.html, rrefsecondfunc.html,
rrefsecondfunc.html, rrefyearfunc.html, rrefyearfunc.html, rrefyearfunc.html
>
>
> All these functions in the reference manual have a sentence like:
> (this is from DAY)
> If the argument is a time duration or timestamp duration: The result is the day part
of the value, which is an integer between -99 and 99. A nonzero result has the same sign as
the argument.
> This can be removed since Derby does not support durations. Then the surrounding text
probably needs re-work as it leaves only a single type of argument.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.