[
https://issues.apache.org/jira/browse/OPENJPA-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922692#comment-17922692
]
Paulo Cristovão de Araújo Silva Filho commented on OPENJPA-2933:
----------------------------------------------------------------
Pinging as requested (;)). Still waiting for PR#122 acceptance to open PR of
this issue (already made it). As I'm out of vacation, OPENJPA-2930 should take
more time to fix, as I need to understand the internals of allowing usage of
java.util.UUID as basic and identity type (see
[here|https://jakarta.ee/specifications/persistence/3.1/jakarta-persistence-spec-3.1#a132]
and
[here|https://jakarta.ee/specifications/persistence/3.1/jakarta-persistence-spec-3.1#a14205]).
> 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)
