Use JPA criteria instead of Hibernate criteria (which is deprecated) in GORM
Open
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
Some discussion with Hibernate team
https://discourse.hibernate.org/t/deprecation-of-hibernate-criteria-and-how-it-we-can-still-prevent-it/788/12?u=graemerocher
Current known problems:
* Query By Example not supported
* Restrictions.sqlRestriction method for custom SQL restrictions
Contributor guide
Research direction
Start with the linked Hibernate discussion and locate GORM's current Hibernate Criteria integration. Check how Query By Example and Restrictions.sqlRestriction are handled, then compare those paths with the JPA Criteria approach. Done means replacing the deprecated Hibernate Criteria usage without losing support for both listed cases, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100