You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Maxim Solodovnik (Jira)" <ji...@apache.org> on 2025/03/16 01:34:00 UTC
[jira] [Updated] (OPENJPA-2933) Implement new date JPA 3.1 JPQL functions and equivalent Criteria API
[ https://issues.apache.org/jira/browse/OPENJPA-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik updated OPENJPA-2933:
--------------------------------------
Fix Version/s: 4.0.2
(was: 4.0.1)
> 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
> Assignee: Maxim Solodovnik
> Priority: Major
> Fix For: 4.0.2
>
>
> 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)