[
https://issues.apache.org/jira/browse/OPENJPA-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916717#comment-17916717
]
Paulo Cristovão de Araújo Silva Filho commented on OPENJPA-2933:
----------------------------------------------------------------
I've also implemented this issue, but, as there are some dependencies with
OPENJPA-2908 and OPENJPA-2932 (and conflicts to solve), I'll wait until PRs 121
and 122 are accepted to make the pull request. Tested the changes successfully
on derbydb, h2, postgresql and mysql, although there are failing unrelated
tests.
If anyone wants to check the current code, please refer to [the forked
branch|https://github.com/cristof/openjpa/tree/OPENJPA-2933].
> Implement new date JPA 3.1 JPQL functions and equivalent Criteria API
> ---------------------------------------------------------------------
>
> Key: OPENJPA-2933
> URL: https://issues.apache.org/jira/browse/OPENJPA-2933
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Paulo Cristovão de Araújo Silva Filho
> Priority: Major
>
> As noted in OPENJPA-2930, although version 4.0.1 claims to be JPA 3.1
> compatible, pom.xml declared api is 3.0. There is already a PR (121) bumping
> JPA version, but it doesn't implement the API new features.
> OPENJPA-2932 deals with arithmetic new JPQL functions and Criteria API.
> This issue is meant to control implementation of the new date functions of
> Criteria API ({_}localDate(){_}, _localDateTime()_ and {_}localTime(){_}), as
> well of the following new JPQL functions:
> * LOCAL DATE
> * LOCAL DATETIME
> * LOCAL TIME
> * EXTRACT(datetime_field FROM datetime_expression)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
