Spring JDBC中数据库操作出错时谁会抛出异常？

Great question—this is one of those under-the-hood details that trips up even seasoned Spring developers. Let me break it down step by step:

• The initial error source: When a database issue (like invalid SQL, connection failures, or constraint violations) occurs, the underlying JDBC driver is the first to throw a checked SQLException.
• Spring's translation layer: Spring JDBC uses an SQLExceptionTranslator (usually the default SQLErrorCodeSQLExceptionTranslator or SQLStateSQLExceptionTranslator) to convert that checked SQLException into an unchecked, Spring-specific DataAccessException subclass. This design choice lets you avoid cluttering your code with mandatory try/catch blocks for every database operation.
• The final exception thrower: The core Spring JDBC template classes—most commonly JdbcTemplate or NamedParameterJdbcTemplate—are the ones that ultimately throw these translated exceptions. When you call methods like update() or query(), the template handles raw JDBC calls internally, catches the driver's SQLException, runs it through the translator, and then propagates the Spring exception up to your application code.

For example, if you run a query against a non-existent table:

jdbcTemplate.query("SELECT * FROM non_existent_table", new BeanPropertyRowMapper<>(User.class));

The JDBC driver throws a SQLException, Spring translates it to BadSqlGrammarException, and JdbcTemplate throws that exception for your code to handle (or let propagate to a global exception handler).

One key note: You’ll only ever get a raw SQLException if you use low-level connection access (like JdbcTemplate.execute(ConnectionCallback)), in which case you’re responsible for handling it yourself.

内容的提问来源于stack exchange，提问作者Machacool