spring-projects / spring-projects/spring-data-relational
Optimized writing behavior [DATAJDBC-533]
@schauder is already working on this.
Since Dec 31, 2020.
- Dominant language
- Java
- Stars
- 827
- Forks
- 394
- PR merge metrics
- No merged PRs in 30d
Description
Jens Schauder opened DATAJDBC-533 and commented
Since Spring Data JDBC does not maintain any relationship between loaded and saved entities we always have to write everything.
This issue should explore ways to optimise this behavior.
-
boolean attribute annotated with
isChangedcould mark a complete entity as unchanged (including all referenced entities). -
Wrappers for collections could contain offer a similar attribute to communicate something similar.
a) denoting nothing was added/removed from the collection
b) denoting nothing was added/removed from the collection nor did the elements themselve change
c) giving separate information about if something/what was added/removed -
Alternatively the same information could be made available in a companion object, denoting those parts of the aggregate that need saving.
-
We could execute a full script instead of single statements, cutting down on the number of round trips.
No further details from DATAJDBC-533
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.
Assessment
This issue has not been assessed yet.