-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Jpa criteria support in Hibernate ORM Panache #3965
Comments
In addition to that, can we come up with something like JHipster's entity filtering mechanism? |
There are ongoing discussion in this area in the following issue: #2303 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you! |
If I'm not mistaken, the entity filtering is really how to expose arbitrary query restriction via your REST endpoint, correct @johnbanq? I think it's akin to the simplification of the REST enndpoint |
I agree with @loicmathieu I think the optional predicate will offer the same flexibility as specification and the same type safety once we plug the HQL resolver. I'd prefer we start with this approach before going on the heavyweight Specification approach Spring went to. |
@emmanuelbernard yes, the flexibility is important. Another concern is the Java type-safe query, which is provided by JPA Criteria API. |
JPA Criteria is very important for developers. Hope add Spring Data like
Specification
to build query Criteria and provide variants of existed methods , eg.findAll(Specification, Sort)
.The text was updated successfully, but these errors were encountered: