[
https://issues.apache.org/jira/browse/OPENJPA-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111580#comment-18111580
]
ASF subversion and git services commented on OPENJPA-2956:
----------------------------------------------------------
Commit 3f540597157855cba2df073788d4ff4d40ecffb6 in openjpa's branch
refs/heads/master from Paulo Cristovão de Araújo Silva Filho
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=3f5405971 ]
Merge pull request #178 from apache/OPENJPA-2956
[OPENJPA-2956] Unwrap ID(), honour null precedence and reject set operations in
memory
> In-memory ID(), set ops and nullPrecedence unimplemented
> --------------------------------------------------------
>
> Key: OPENJPA-2956
> URL: https://issues.apache.org/jira/browse/OPENJPA-2956
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 4.2.0
> Reporter: Maxim Solodovnik
> Priority: Major
> Fix For: 4.2.0
>
>
> Discussion thread:
> https://github.com/apache/openjpa/pull/144#discussion_r3683000248
> **(medium)** `getNativeObjectId` returns the same `GetObjectId` as
> `getObjectId`, which evaluates to the internal ObjectId wrapper (e.g.
> LongId), not the raw PK value - so an in-memory `ID(e) = :id` comparison
> against the plain key may never match; should it unwrap like the JDBC side?
> Similarly `setOperands`/`setOperationType` and `nullPrecedence` appear
> consumed only by the JDBC store, so in-memory execution of
> UNION/INTERSECT/EXCEPT or NULLS FIRST/LAST silently produces wrong results -
> should the in-memory path reject or implement them?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
