spring-projects / spring-projects/spring-batch
Refactor JDBC DAOs to use named parameters instead of positional parameters
Open
Nobody has claimed this yet.
in: core
related-to: job-repository
type: enhancement
- Dominant language
- Java
- Stars
- 3k
- Forks
- 2.5k
- Avg merge
- 6d 53m
- Merged PRs (30d)
- 3
Description
It will eliminate duplicate parameters from java code although JDBC prepared statement does not.
And migrate from JdbcTemplate to NamedParameterJdbcTemplate or fluent JdbcClient?
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 locating the JDBC DAOs and reviewing their current JdbcTemplate usage. Compare NamedParameterJdbcTemplate with fluent JdbcClient in the project's Spring context, then define which option should be used and how all relevant DAOs can avoid duplicate parameters while preserving behavior; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100