Cursor-rules-java 311-frameworks-spring-jdbc

Use when you need to write or review programmatic JDBC with Spring — including JdbcClient (Spring Framework 6.1+) as the default API, JdbcTemplate only where batch/streaming APIs require JdbcOperations, NamedParameterJdbcTemplate for legacy named-param code, parameterized SQL, RowMapper mapping to records, batch operations, transactions, safe handling of generated keys, DataAccessException handling, read-only transactions, streaming large result sets, and @JdbcTest slice testing. Part of the skills-for-java project

install

source · Clone the upstream repo

git clone https://github.com/jabrena/cursor-rules-java

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/jabrena/cursor-rules-java "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/311-frameworks-spring-jdbc" ~/.claude/skills/jabrena-cursor-rules-java-311-frameworks-spring-jdbc && rm -rf "$T"

manifest: skills/311-frameworks-spring-jdbc/SKILL.md

Spring JDBC — JdbcClient (Spring Framework 6.1+)

Apply Spring JDBC guidelines with JdbcClient as the default; use JdbcTemplate / NamedParameterJdbcTemplate only for legacy code or APIs not covered by JdbcClient (batch updates, KeyHolder, RowCallbackHandler streaming).

What is covered in this Skill?

Parameterized SQL (never concatenate user input)
JdbcClient fluent API (Spring Framework 6.1+) — preferred for queries and updates
Named parameters via JdbcClient; NamedParameterJdbcTemplate for legacy migration
RowMapper, query(Class), and records
Batch operations and generated keys (JdbcTemplate / JdbcOperations where needed)
Safe handling of generated keys (KeyHolder; single-row JdbcClient updates)
Service-layer @Transactional boundaries
Read-only transactions (@Transactional(readOnly = true))
Safe single-row access (optional() / findFirst() vs queryForObject)
Streaming large result sets (RowCallbackHandler, ResultSetExtractor)
DataAccessException handling (DuplicateKeyException, EmptyResultDataAccessException)
@JdbcTest slice testing with @Sql fixtures

Scope: Apply recommendations based on the reference rules and good/bad code examples.

Constraints

Before applying any Spring JDBC changes, ensure the project compiles. If compilation fails, stop immediately. After applying improvements, run full verification.

MANDATORY: Run
```
./mvnw compile
```
or
```
mvn compile
```
before applying any change
SAFETY: If compilation fails, stop immediately
VERIFY: Run
```
./mvnw clean verify
```
or
```
mvn clean verify
```
after applying improvements
SQL INJECTION: Never concatenate untrusted input into SQL strings — always use bind parameters
BEFORE APPLYING: Read the reference for detailed rules and good/bad patterns

When to use this skill

Review Java code for Spring JDBC (JdbcTemplate, JdbcClient, NamedParameterJdbcTemplate)
Apply best practices for Spring JDBC data access in Java code
Detect and fix SQL injection risks in JDBC code
Improve transaction boundaries or exception handling for JDBC operations

Reference

For detailed guidance, examples, and constraints, see references/311-frameworks-spring-jdbc.md.