-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add subquery(EntityType) to javax.persistence.criteria.CriteriaQuery #71
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
|
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Aug 17, 2023
This is a perfectly sensible and straightforward request. I've added the missing overload to |
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Aug 24, 2023
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Aug 24, 2023
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Aug 24, 2023
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Aug 24, 2023
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Aug 24, 2023
gavinking
added a commit
to gavinking/persistence
that referenced
this issue
Aug 24, 2023
lukasj
pushed a commit
that referenced
this issue
Aug 25, 2023
done in #467 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If using dynamic entities not defined by classes (as is the case when using EntityMode.MAP), there's no way to create a subquery. This is because javax.persistence.criteria.CriteriaQuery.subquery() takes an entity Class as an argument, and unlike javax.persistence.criteria.CriteriaQuery.from() there's no overloaded method to subquery by EntityType. This severely limits what can be done using entities mapped with EntityType for which there is no Java class.
The text was updated successfully, but these errors were encountered: