spring-projects / spring-projects/spring-data-jpa
Use entity graphs on base entity instead of tuple selects for projections.
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Using tuples makes spring data responsible for selecting the right thing and doesn't work for collection valued attributes at all.
See #2078, #1623
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review issues #2078 and #1623 first, then trace how projections currently use tuple selects. Confirm the intended entity-graph behavior on the base entity, especially for collection-valued attributes, and use those references to define when the projection handling is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100