[
https://issues.apache.org/jira/browse/OPENJPA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080600#comment-18080600
]
ASF subversion and git services commented on OPENJPA-2940:
----------------------------------------------------------
Commit ee642211c3e59cad35c45eddcd24d64dd9df9dcf in openjpa's branch
refs/heads/OPENJPA-2940 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=ee642211c ]
[OPENJPA-2940] Cap getSingleResultOrNull row scan to detect non-uniqueness
Per PR #142 review feedback, the new getSingleResultOrNull() only
needs to distinguish zero, one or more-than-one rows. Without a
row cap, JPQL queries like em.createQuery("select e from Entity e")
.getSingleResultOrNull() load every matching row just to throw
NonUniqueResultException.
Save the current max-results, lower it to 2 for the duration of
the call (preserving any tighter user-supplied limit), and restore
in finally. Detection semantics are unchanged — size() > 1 still
fires when more than one row matches.
Verified: TestGetSingleResultOrNull (5/5), TestQueryResults (24/24)
and TestQueryConvertPositionalParameters (5/5) pass on Derby.
> Implement Jakarta Persistence 3.2
> ---------------------------------
>
> Key: OPENJPA-2940
> URL: https://issues.apache.org/jira/browse/OPENJPA-2940
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Paulo Cristovão de Araújo Silva Filho
> Priority: Major
> Attachments: image-2026-03-28-14-55-26-463.png
>
>
> Implement Jakarta Persistence API 3.2 as prescribed by
> [specification|https://jakarta.ee/specifications/persistence/3.2/] and
> required by Jakarta EE 11.
> This change requires JDK17 or higher compatibility and needs considerable
> checks.
> I've already pushed a branch (WIP) without the proper API bump, focusing on
> updating dependencies while keeping the project passing its current tests at
> least in default profile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
