[
https://issues.apache.org/jira/browse/DERBY-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127453#comment-14127453
]
Kim Haase commented on DERBY-1927:
----------------------------------
I think TIMESTAMP may be the only relevant topic where this sentence is not
used. My best guess is that the sentence applies only to the two-argument form
of the function, assuming it applies at all.
It's used in functions that return numeric values from strings or that return
part of a time value as an integer. I'm not sure that TIMESTAMP fits into this
category.
There's an error in the topic on the SECOND function. The second sentence says,
"If the argument is null, the result is 0." To be consistent, "0" should be
"the null value".
These are the relevant topics.
BIGINT
CHAR
DOUBLE
INTEGER
SMALLINT
DATE
DAY
HOUR
MINUTE
MONTH
SECOND
TIME
YEAR
> Built-in Functions incorrect specification of null arguement
> ------------------------------------------------------------
>
> Key: DERBY-1927
> URL: https://issues.apache.org/jira/browse/DERBY-1927
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.6
> Reporter: Laura Stewart
> Priority: Minor
> Labels: derby_triage10_11
>
> Inconsistent use of the statement 'If the argument can be null, the result
> can be null;
> if the argument is null, the result is the null value.' throughout the
> built-in functions section.
>
> For example the TIME function has this statement, while the TIMESTAMP
> function does not, but
> the result of passing in a null argument are the same (a return value of
> null.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
