arangodb / arangodb/spring-data
Auto-persistence of associations with null ids would be beneficial (for users & ArangoDB)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 116
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
For instance, for the
https://github.com/arangodb/spring-data#reference
example, when address.id is null, it's not currently auto-persisted; thus it currently has to be persisted separately (prior to persisting the parent entity). In JPA implementations i've worked with, the association(s) would be auto-persisted (allowing to persist an entire aggregate[1] by making only 1 call to persist the aggregate root).
I think it would be beneficial (for users & ArangoDB) if arangodb/spring-data functioned similarly: it would make development easier, & facilitate adoption of ArangoDB. The implementation also shouldn't be difficult...
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
Start with the linked spring-data reference example and inspect how an aggregate root and its associations are persisted when address.id is null. Trace the association persistence entry point and compare the current behavior with the requested JPA-style cascade. Done means one persist call stores both the parent and the new associated entity; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100