Greg L. Turnquist

This is pending https://github.com/eclipse-ee4j/jpa-api/issues/76.

In the other ticket (https://github.com/spring-projects/spring-data-jpa/issues/2380#issuecomment-988663924), we couldn't get more details on what was going wrong for that user. As stated, we use JDK proxies for limited purposes. The proxies that...

I'm closing this ticket as it appears identical to the issues popping up in the #2380, which was not actionable on our end. PLUS, that ticket has tips on how...

So far, this appears to be a wrinkle to our subquery detecting logic, which is removes `(from ....)` subqueries. You have the classic `select 1 from ...` variation. It seems...

The fix was merged into https://github.com/spring-projects/spring-data-jpa/commit/91cd84e7061c0c655128624d34a0ff41d1f58d7a and additional test cases from the other PRs were folded into https://github.com/spring-projects/spring-data-jpa/commit/f7737014944e606686ca5111574229426ec4484b.

Backported to `2.7.x.` and `2.6.x`.

The issue still lingers on EclipseLink's bug tracker.

Spring Data JPA now uses JPA's `between()` operator... ```java case BETWEEN: ParameterMetadata first = provider.next(part); ParameterMetadata second = provider.next(part); return builder.between(getComparablePath(root, part), first.getExpression(), second.getExpression()); ``` ...so I'm not sure this...

How does this stack of feature tie into using the [newly added JSqlParser](https://github.com/spring-projects/spring-data-jpa/commit/1fe4cf598d7087ad8d434eb7b99bff90e033f164)?

@DiegoKrupitza In light of your latest comments, then this makes sense, if you wish to proceed with working up a modification.