[jira] [Commented] (JDO-749) Support for java.time types, and querying using associated methods

["Andy Jefferson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JDO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005255#comment-15005255 ] 

Andy Jefferson commented on JDO-749:
------------------------------------

Actually, after doing a few tests with Java7 and Java8, we cannot simply add Java8 related classes to jdo-api compile to 1.8 and run with 1.7, since some operations have a check on major.minor version and it finds the jdo-api with major.minor as 52.0. 

Ways around this are
1. Have 2 jdo-api jars. One for java7 and one for java8 (with the java.time support), and the user pulls in the one they require.
2. Just move to java8 minimum

> Support for java.time types, and querying using associated methods
> ------------------------------------------------------------------
>
>                 Key: JDO-749
>                 URL: https://issues.apache.org/jira/browse/JDO-749
>             Project: JDO
>          Issue Type: New Feature
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>             Fix For: JDO 3.2
>
>
> Refer to an associated issue for JPA for what support should look like
> https://java.net/jira/browse/JPA_SPEC-63
> The methods that should be supported in queries would initially be
> LocalDateTime : getDayOfMonth, getMonth, getYear, getHour, getMinute, getSecond
> LocalTime : getHour, getMinute, getSecond
> LocalDate : getDayOfMonth, getMonth, getYear
> These would need to be part of JDOQL string-based, as well as the JDOQLTypedQuery (hence have equivalent Expression classes).
> Note that all of these are already implemented in DataNucleus, and there are JDOQLTypedQuery expression classes available.
> Timing of this simply depends on the JRE that the next release of JDO is targetted at, since this needs Java 8.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)