spring-projects / spring-projects/spring-data-relational
Support read after write logic
Open
Nobody has claimed this yet.
type: enhancement
- Dominant language
- Java
- Stars
- 827
- Forks
- 394
- PR merge metrics
- No merged PRs in 30d
Description
In order to utilise triggers and default values a read-after-write logic should be supported.
see also https://github.com/spring-projects/spring-data-commons/issues/2158
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
No files, tests, or entry points are named. Start by reading the linked Spring Data Commons issue and tracing the Spring Data JDBC and R2DBC write paths. Done means supporting a read after write so database triggers and default values are reflected.
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
- 20/100