[
https://issues.apache.org/jira/browse/OPENJPA-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119523#comment-18119523
]
ASF subversion and git services commented on OPENJPA-2949:
----------------------------------------------------------
Commit 2e3a9217bf1b860bc66a9de480d48c43c6afedca in openjpa's branch
refs/heads/OPENJPA-2949-docs from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=2e3a9217b ]
[OPENJPA-2949] Document the ID()/VERSION() comparison operators and in-memory
set operations
> ID()/VERSION() limited to equality against parameters
> -----------------------------------------------------
>
> Key: OPENJPA-2949
> URL: https://issues.apache.org/jira/browse/OPENJPA-2949
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 4.2.0
> Reporter: Maxim Solodovnik
> Assignee: Romain Manni-Bucau
> Priority: Major
> Fix For: 4.2.0
>
>
> Discussion link:
> [https://github.com/apache/openjpa/pull/144#discussion_r3682999176]
> *(medium)* {{entity_id_or_version_comp()}} only allows {{ID( x )/VERSION( x
> )}} compared with {{=/<>}} against an input parameter. Spec-legal forms like
> {{{}ID(e) = 5{}}}, {{VERSION(e) >= :v}} or {{ID(a) = ID(b)}} do not parse -
> intentional first step, or should these functions be reachable from the
> general comparison/arithmetic productions?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
