spring-projects / spring-projects/spring-session
Consider adding logging when JDBC repo operations don't affect expected row count
Open
Nobody has claimed this yet.
in: jdbc
type: enhancement
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
See #1031 for background.
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 by reading issue #1031 for the background, then locate the JDBC repository operations that check affected row counts. Done means adding logging for cases where the operation does not affect the expected number of rows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100