[
https://issues.apache.org/jira/browse/DERBY-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner closed DERBY-725.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.2.1.6
Assignee: Jeff Levitt
Confirmed fixed by inspection of the page in the ref manual for 10.2
> NULLIF and CASE expressions section in reference manual contains two stale
> paragraphs.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-725
> URL: https://issues.apache.org/jira/browse/DERBY-725
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.1.2.1
> Reporter: Daniel John Debrunner
> Assigned To: Jeff Levitt
> Priority: Trivial
> Fix For: 10.2.1.6
>
> Attachments: derby725.diff, rrefcasenullif.html
>
>
> The two paragraphs below from 10.1 ref manual, page 78 in pdf can be removed.
> ----------------------------------------------------------------------------------------------------
> You do not need to use the CASE expression for avoiding NullPointerExceptions
> when a
> nullable column becomes a method receiver.
> If the value of the instance specified in an instance method invocation is
> null, the result of
> the invocation is null (SQL NULL). However, you still might need to use the
> CASE
> expression for when a nullable column is a primitive method parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
