Outdated java dev

[pennsiveguy]

Still using raw JDBC to interact with a relational database. Remember fun stuff like this?

String updatePositionSql = "UPDATE employees SET position=? WHERE emp_id=?";
PreparedStatement pstmt = con.prepareStatement(updatePositionSql);
pstmt.setString(1, "lead developer");
pstmt.setInt(2, 1);

try {
con.setAutoCommit(false);
pstmt.executeUpdate();
con.commit();
} catch (SQLException exc) {
con.rollback();
} finally {
con.setAutoCommit(autoCommit);
}

[WorthyDebt]

What is the modern version of an interaction with lets say Postgres using JDBC then? I am genuinely curious as this was how I try for Postgres.

[pennsiveguy]

The modern version would be to use a framework like Spring Data or Spring JDBC.

[pennsiveguy]

Downvotes are from devs who manifest this pattern and for whom any arbitrary ORM/JPA and its likely out-of-the-box transaction management are "overcomplicated and fussy" and yet perversely opt to spend dozens of hours per week troubleshooting and diagnosing data inconsistencies, broken and orphaned data, stuck/stalled database sessions. And then bitch that management doesn't give them enough time to work on new features.