[
https://issues.apache.org/jira/browse/JDO-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144485#comment-15144485
]
Tilmann Zäschke commented on JDO-751:
-------------------------------------
I don't think querying for {{null}} is conceptually wrong. It would be wrong if
{{Optional}} would be a property of a reference, but it's not a property, it's
an own class/type. If we don't want people to query for 'null' then we should
make sure that they can't and forbid it. But I don't think that would be a good
idea. In Java the semantic is clearly that a reference to Optional is distinct
from a reference from Optional to something else. I'm not convinced that a
JDOQL should behave different here.
> Support for Java8 Optional
> --------------------------
>
> Key: JDO-751
> URL: https://issues.apache.org/jira/browse/JDO-751
> Project: JDO
> Issue Type: New Feature
> Components: specification, tck
> Reporter: Andy Jefferson
>
> java.util.Optional provides a feature that is available in other languages.
> Since JDO 3.2 will be for Java8+ then it makes sense to add support for this
> as a "supported persistable type"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
